#federal_aviation_administration

Air Traffic Controllers Warned Trump Helicopter Pilots About Radio Failures a Week Before Near-Miss with Jet Federal investigators revealed that air traffic controllers in Washington and the pilots of President Donald Trump’s helicopter met to address communication issues one week before a jet was allowed to take off as Marine One departed the White House. The National Transportation Safety Board’s preliminary report highlighted that controllers did not receive the standard three-minute warning call ahead of Marine One flights, prompting an alternative plan to relay the radio call through a third party. However, this plan also failed on the day of the Aug. 4 incident near Ronald Reagan Washington National Airport. The NTSB’s findings indicated that the absence of the three-minute warning call led to both the jet and helicopter being airborne simultaneously, which violated safety protocols established after last year’s midair collision near the airport that killed 67 people. Despite this, officials emphasized that the president was never in danger. The Pentagon has a longstanding agreement with the Federal Aviation Administration (FAA) to provide controllers with a three-minute warning before the president’s helicopter takes off, a protocol that predates the 2025 crash. Recordings from the air traffic control tower showed that controllers did not hear the calls from Marine One’s pilot warning of the helicopter’s imminent departure. However, separate recordings posted by ATC.com revealed that the helicopter did make those calls. The helicopter pilots attempted to relay the three-minute warning through the facility at Joint Base Anacostia-Bolling, but this effort was unsuccessful.#president_donald_trump #federal_aviation_administration #national_transportation_safety_board #air_traffic_controllers #joint_base_anacostia_bolling

Aerospace X1: World's Largest Electric Aircraft Took Flight, Cost Just 480 Rupees The aerospace startup Heart Aerospace successfully completed its first test flight of the X1, a groundbreaking all-electric aircraft. The flight, which took place on August 12 at Plattsburgh International Airport in New York, marked a significant milestone in the aviation industry. The X1, described as the world’s largest electric aircraft, flew for 27 minutes, reaching an altitude of 1,100 feet. The energy consumption during the flight was minimal, with the total electricity cost amounting to just 5 dollars—equivalent to approximately 480 rupees. This achievement highlights the potential of electric propulsion to revolutionize air travel. The X1 is a large aircraft, measuring 106 feet in length and 76 feet from nose to tail. Despite its size, it operates entirely on battery power, with a takeoff weight of over 25,000 pounds (11,340 kilograms). The test flight demonstrated the aircraft’s ability to sustain flight using its electric powertrain, which delivered over 1 megawatt of power. The success of this flight is seen as a major game-changer for the aviation sector, offering a sustainable alternative to traditional fuel-based aircraft. Heart Aerospace’s X1 serves as a test platform for future developments, including the ES-30, a hybrid-electric aircraft designed to reduce operational costs for regional airlines. The company claims the ES-30 could cut operating expenses by over 40%, making it a viable option for short-haul flights. The ES-30 would accommodate 30 passengers and travel up to 804 kilometers (500 miles) on a single charge. In hybrid mode, combining electric and traditional fuel systems, the aircraft could extend its range to 1,250 kilometers (800 miles).#federal_aviation_administration #heart_aerospace #x1 #plattsburgh_international_airport #es_30

Delta Flight Investigates Hoax Wi-Fi Network on Route to Atlanta A cybersecurity incident involving a fraudulent Wi-Fi network on a Delta Airlines flight to Hartsfield-Jackson Atlanta International Airport is under investigation. The event occurred on Delta flight 591, which departed Las Vegas for Atlanta on August 10. According to a Delta spokesperson, the unauthorized network briefly appeared during the flight but did not compromise any onboard systems. The airline’s cabin crew disabled the Boeing 757’s Wi-Fi functionality for approximately 30 minutes as a precaution. No emergency was reported to air traffic control, and the spokesperson emphasized that flight safety was never at risk. The airline confirmed there was no data breach or system hacking, though the incident is being examined to determine its origin and scope. Delta stated it is collaborating with federal law enforcement agencies and aviation regulators to investigate the matter thoroughly. The spokesperson thanked the crew for their professionalism and urged passengers to remain patient during the inquiry. Federal authorities have previously warned about similar incidents, which are classified as “evil twin attacks.” In such cases, hackers deploy fake Wi-Fi networks with stronger signals than legitimate ones, tricking users into connecting. Once connected, attackers can intercept sensitive data, such as login credentials or financial information. The Federal Aviation Administration (FAA) noted it is aware of the report but assured travelers that breaches of onboard Wi-Fi systems do not impact the aircraft’s flight safety. The incident coincided with DEF CON 34, a major hacking conference held in Las Vegas over the weekend.#hartsfieldjackson_atlanta_international_airport #las_vegas #federal_aviation_administration #delta_airlines #def_con_34

JetBlue Pilot Reports Drone Collision During Landing Approach at JFK Airport A JetBlue Airways pilot reported a drone collision as the flight approached landing at John F. Kennedy International Airport in New York City on Monday morning, June 29, 2026. The incident occurred around 7:15 a.m. when the aircraft was at approximately 3,000 feet altitude, according to the pilot’s communication with air traffic control. The pilot described the collision as happening during a turn while the plane was transitioning to the approach path, stating, “We collided with a drone back there in the turn as we were coming to ASALT, just wanted to pass to you.” The affected flight, JetBlue 948, was en route from Las Vegas and had no immediate need for assistance, the pilot reported. The plane safely landed at Terminal 5 without any injuries to passengers, crew, or pilots. A post-flight inspection of the aircraft did not reveal any structural damage, though the Federal Aviation Administration (FAA) has initiated an investigation into the incident. JetBlue Airways reiterated its commitment to safety in a statement, noting, “Safety is JetBlue’s first priority, and we will assist with any relevant investigations.” The incident follows a similar report from a United Airlines pilot earlier in the week, who described nearly colliding with a drone while landing at Newark Liberty International Airport. The FAA has previously warned that unauthorized drone activity near airports and flights is illegal, with operators facing fines, criminal charges, or even jail time under federal law. Despite these regulations, the FAA noted receiving over 100 drone sightings near airports each month, highlighting the persistent risk posed by unregulated drone operations.#federal_aviation_administration #abc #john_f_kennedy_international_airport #jetblue_airways #john_nance

FAA Requires SpaceX to Conduct Mishap Investigation Before Resuming Starship Launches The Federal Aviation Administration (FAA) has mandated that SpaceX complete a formal mishap investigation into the May 22 Starship Flight 12 mission before resuming launches of the Starship-Super Heavy rocket. The decision follows an analysis of the flight, which ended in an off-nominal performance of the Super Heavy booster, tail number Booster 19, leading to a mishap. The FAA’s statement, released on May 27, emphasized that the agency would oversee the investigation, participate in all stages, and approve SpaceX’s final report, including any corrective actions. The mishap occurred during the ascent phase of Flight 12. At approximately 1 minute and 42 seconds into the mission, one of the 33 Raptor V3 engines on the Super Heavy booster failed. Less than a minute later, SpaceX initiated a staged shutdown of engines as it approached stage separation. The on-screen graphics showed 12 of 13 center engines ignited at the 2-minute, 32-second mark, but as the outer ring began re-igniting, several engines were shown as non-operational, deviating from the planned sequence. Dan Huot, a SpaceX communications team member, noted during the broadcast that the company observed “six good engines on ship” and described the event as an “early boostback shutdown.” SpaceX’s post-mission assessment detailed the sequence of events. After stage separation, the Super Heavy booster executed a directional flip maneuver and attempted a boostback burn. However, it failed to ignite all planned engines, resulting in a partial burn that ended prematurely. The booster then attempted to reignite engines for the landing burn but ultimately experienced a hard splashdown in the Gulf of America.#spacex #federal_aviation_administration #starship_flight_12 #super_heavy_booster #raptor_v3_engine

FAA Requires Mishap Investigation into Latest Starship Launch The Federal Aviation Administration has mandated that SpaceX conduct a formal investigation into its latest Starship test flight, which the agency classified as a mishap. The incident occurred during the May 22 Flight 12 mission from SpaceX’s Starbase facility in Texas. The FAA’s determination followed an assessment of the launch’s anomalies, which included significant failures in the Super Heavy booster’s performance. The agency’s classification of the event as a mishap triggers a requirement for SpaceX to submit a detailed report and corrective actions for FAA approval before resuming Starship flights. The Flight 12 launch aimed to test the upgraded version 3 of Starship, featuring enhancements to both the Super Heavy booster and the upper stage, including the introduction of Raptor 3 engines. SpaceX planned for the Super Heavy to perform a “boostback” maneuver after the upper stage separated, guiding it toward a controlled splashdown in the Gulf of Mexico. However, the booster encountered multiple engine failures shortly after initiating the boostback burn. The maneuver, intended to last about a minute, was aborted after less than 20 seconds. The faulty booster then plummeted into the Gulf at speeds exceeding 1,500 kilometers per hour, as confirmed by telemetry data streamed during the SpaceX webcast. The FAA noted that the incident triggered a debris response area, though no damage was reported. The anomaly also caused disruptions to air traffic, with several aircraft experiencing delays or airborne holding events due to the debris field.#spacex #federal_aviation_administration #starship #starbase #flight_12

United Airlines Passenger Allegedly Assaulted Flight Attendant, Attempted to Enter Cockpit A United Airlines passenger was detained after allegedly assaulting a flight attendant and attempting to access the cockpit during a flight arriving at Newark Liberty International Airport on Saturday evening. The incident occurred on United Flight 1837, which had arrived in New Jersey from the Dominican Republic around 6:25 p.m. The 48-year-old man, whose name was not disclosed, was removed from the aircraft by law enforcement. According to the Port Authority Police Department, he was taken to a hospital for a psychiatric evaluation, while a second individual on board declined medical attention. No other injuries were reported. Air traffic control audio captured the incident, with the pilot informing controllers of the situation. “A gentleman just attacked one of the flight attendants and is trying to open the forward main cabin door,” the pilot stated. The controller responded with alarm, saying, “Oh, my God,” before the pilot added, “Trying to access the flight deck.” United Airlines confirmed that law enforcement assisted the flight in handling the unruly passenger. In a statement, the airline expressed gratitude to the crew for their efforts to “ensure the safety of fellow crew members and our customers.” The Federal Aviation Administration (FAA) announced it would investigate the incident. FAA data shows that nearly 500 unruly passenger reports have been filed so far this year, with 110 of those coming in April alone. The agency’s records indicate that unruly passenger incidents reached an all-time high of 5,973 in 2021 but have since declined. In 2025, the number dropped to 1,621.#federal_aviation_administration #united_airlines #newark_liberty_international_airport #port_authority_police_department #united_flight_1837

Delta Flight Delayed After Passenger Refuses to End Phone Call Before Takeoff A Delta Air Lines flight bound for Atlanta, Georgia, faced a significant delay after a passenger refused to end a phone call before takeoff, prompting the aircraft to return to the gate. The incident occurred on Monday evening when Delta Flight 1323 was departing from Miami International Airport. A woman in business class ignored repeated instructions from flight attendants to end her cellphone call while the plane was taxiing to the runway. The situation escalated as the passenger became disruptive, leading the airline to declare the situation a safety concern. According to Delta’s statement, the crew attempted to de-escalate the situation by asking the passenger to end her call. However, the woman continued using her phone and reportedly directed profanity toward flight attendants and other passengers seated nearby. A passenger seated near her told WAGA-TV in Atlanta that the woman’s behavior was uncooperative and escalated tensions among the cabin. Flight attendants eventually announced that the aircraft would need to return to the gate to remove the disruptive passenger. Once the plane reached the gate, the woman refused to leave, prompting authorities to be called. The airline’s crew then instructed all passengers to deplane, which caused frustration among the more than 160 passengers onboard. Some passengers expressed anger at the situation, with one person overheard saying, “So, we’re all supposed to listen and [she] doesn’t?” The woman eventually attempted to deplane with the other passengers but was arrested on a charge of trespassing after a warning, according to Miami-Dade County court records.#delta_air_lines #miami_dade_county #federal_aviation_administration #miami_international_airport #waga_tv

SFO Flight Disruptions Trigger Widespread Delays and Cancellations on April 9, 2026 San Francisco International Airport faced unprecedented operational chaos on April 9, 2026, as newly implemented Federal Aviation Administration (FAA) rules on arrival procedures caused 144 flight delays and nine cancellations. The disruptions impacted over 18,000 passengers across domestic and international routes, with cascading effects rippling through major hubs in Los Angeles, Portland, Munich, Toronto, and Vancouver. Delta Air Lines, United Airlines, Alaska Airlines, Lufthansa, and Air Canada reported extended ground holds and compressed turnaround windows, which disrupted same-day connections and strained airline operations. The FAA’s restrictive landing protocols at SFO aimed to limit simultaneous approach configurations during peak arrival periods, reducing the airport’s concurrent landing capacity below historical norms. These measures, designed to manage air traffic during high-demand times, created disproportionate disruption when airlines relied on tight connection windows and limited recovery periods. Industry analysts noted that the new rules would persist beyond April 9, exacerbating chronic bottlenecks at SFO during peak travel seasons and adverse weather. The April 9 incident validated earlier forecasts by aviation monitoring services, which had warned of fragile operating conditions at the Bay Area hub. Major carriers scrambled to mitigate the fallout. Delta, United, and Alaska Airlines—key operators at SFO—experienced rolling departure delays that compressed equipment turnaround windows and forced crew scheduling adjustments. Late-arriving aircraft extended ground times, creating ripple effects across subsequent flight legs.#delta_air_lines #federal_aviation_administration #united_airlines #alaska_airlines #san_francisco_international_airport

Europe Faces Jet Fuel Shortage Amid Chicago O'Hare Flight Cuts Officials in Europe have warned that the continent is facing a critical jet fuel shortage, with reserves expected to last only six weeks. This development has raised concerns about potential flight cancellations, which could ripple across global travel networks, including U.S. destinations. Meanwhile, the Federal Aviation Administration (FAA) has announced sweeping changes to flight schedules at Chicago O'Hare International Airport, the busiest in the nation, as part of efforts to address safety concerns and resolve a dispute between major airlines. The FAA’s order mandates a reduction of over 300 daily flights at O'Hare starting May 17, with the cuts remaining in place until October 24. Transportation experts suggest this measure is a direct response to the escalating conflict between American and United Airlines, which has led to an unsustainable increase in air traffic. The FAA cited a lack of air traffic controllers as a key factor in its decision, emphasizing that the current infrastructure cannot handle the volume of flights. DePaul University transportation professor Joe Schwieterman explained that the move aims to "cool down" the situation, with United Airlines likely bearing the brunt of the cuts due to its larger share of O'Hare’s routes. Passengers have expressed alarm over the potential impact of these changes. Antoinette Gonzales, a frequent traveler, warned that the cuts would "increase costs" and create logistical challenges, while Mike Milanowski, a business traveler, noted that the disruptions could complicate his ability to move quickly during the summer.#strait_of_hormuz #federal_aviation_administration #united_airlines #american_airlines #chicago_ohare_international_airport

Hawaiian Airlines Pilots Must Shave Off Beards Later This Month As Alaska Airlines Overturns Rare Exemption Pilots at Hawaiian Airlines will be required to shave their beards by April 20 as part of the airline’s merger with Alaska Airlines. This change aims to standardize operating protocols under a single operating certificate, aligning the carrier’s practices with those of Alaska Airlines. The decision marks the end of a long-standing policy that allowed Hawaiian pilots to maintain beards, a practice rooted in cultural traditions and a differing interpretation of Federal Aviation Administration (FAA) guidelines. For years, Hawaiian Airlines pilots have been permitted to wear beards, a policy that stood in contrast to most U.S. carriers, which typically prohibit facial hair for pilots. This exception was partly due to cultural sensitivities in Hawaii and a historical interpretation of FAA guidance. However, the merger with Alaska Airlines has prompted a shift toward uniformity in operational standards, including grooming and uniform requirements. The FAA has never explicitly banned beards for pilots, but an advisory circular from the 1980s raised concerns about the potential impact of facial hair on the functionality of special air-tight oxygen masks. The circular warned that beards might compromise the seal of these masks, which are critical for pilot safety during decompression events. While the FAA has not issued a blanket ban, many airlines have adopted this guidance to enforce facial hair restrictions. Hawaiian Airlines, however, had been an outlier in this regard. The airline’s policy allowed beards, a stance that faced scrutiny as the merger with Alaska Airlines progressed.#federal_aviation_administration #alaska_airlines #hawaiian_airlines #scott_day #dave_mets

United Airlines Flight Avoids Collision With Military Helicopter in California The Federal Aviation Administration is investigating after a military helicopter crossed into the path of United Airlines Flight 589 near John Wayne Airport in Orange County, California. The incident occurred on Tuesday around 8:40 p.m., according to the FAA, which is examining whether visual separation protocols were followed during the encounter. The agency had recently suspended the practice of visual separation, requiring air traffic controllers to actively manage flight paths for helicopters and commercial aircraft near busy airports. United Airlines Flight 589 was descending toward the airport when a Sikorsky Black Hawk helicopter, identified as a U.S. Army aircraft via flight tracking data, entered its flight path. The FAA stated it is reviewing whether the pilots or controllers adhered to the new rules, which replaced the previous system allowing pilots to manage their own spacing in crowded airspace. The change followed a fatal crash in 2023 when an Army Black Hawk collided with American Airlines Flight 5342 near Reagan National Airport, killing all 67 people on board. The pilots of the helicopter had been granted visual separation clearance minutes before the collision. In a statement, United Airlines confirmed that air traffic controllers had warned the pilots of Flight 589 about the approaching military helicopter. The crew reported seeing the aircraft and responding by leveling off instead of continuing their descent. The plane, carrying 162 passengers and six crew members, landed safely without incident. The FAA’s decision to end visual separation came amid heightened safety concerns after the 2023 crash.#federal_aviation_administration #united_airlines #reagan_national_airport #john_wayne_airport #sikorsky_black_hawk

United flight narrowly avoids US military helicopter in California A United Airlines flight carrying 162 passengers and six crew members narrowly avoided a collision with a US military helicopter near John Wayne Airport in southern California, prompting an investigation by the Federal Aviation Administration (FAA). The incident occurred around 8:40 p.m. on Tuesday when the military Black Hawk helicopter, returning from a training mission, crossed into the path of the passenger plane. Pilots were instructed to alter their course to prevent a collision, according to FAA officials. The FAA announced on Friday that it was examining the incident, which involved a close call just over a year after a similar crash in Washington, D.C., where an American Airlines jet collided with an army Black Hawk helicopter, killing 67 people. That tragedy had led to increased scrutiny of flight path regulations and safety protocols to prevent such near misses. In March, the FAA revised its policy in response to the 2025 crash, requiring air traffic controllers to actively use radar to guide both helicopters and planes around airports nationwide. Previously, controllers relied on pilots to visually avoid each other. Before the Washington incident, controllers had asked helicopter pilots whether they had seen the plane and allowed them to proceed without further intervention. In the California incident, the FAA stated it would assess whether the new rule was applied. United Airlines confirmed the details of the event in a brief statement, noting that pilots on flight 589 were alerted by air traffic control to watch for a military helicopter near the airport. The pilots spotted the helicopter and responded to a traffic alert by leveling the aircraft.#california #federal_aviation_administration #united_airlines #black_hawk_helicopter #john_wayne_airport

A Breezy Weekend Ahead as Arizona Prepares for Cooler Temperatures Phoenix, Arizona, is set to experience a slight cooldown this weekend after hitting another record high temperature on Friday. Saturday’s high is expected to remain in the upper 90s, though this is still significantly above the average high of 81 degrees for this time of year. Meteorologists anticipate a weak weather disturbance moving through the state, which will introduce some clouds and breezy conditions. Easterly winds are forecasted to reach speeds of 15 to 25 mph in the afternoon. The low clouds that formed Saturday morning caused temporary disruptions at Phoenix Sky Harbor International Airport, leading to ground stops for incoming and outgoing flights, as reported by the Federal Aviation Administration. This system may also bring scattered showers and thunderstorms to Northern Arizona on Sunday and Monday. While the heat wave is expected to persist through Tuesday, with temperatures remaining in the 90s, a low-pressure system is set to arrive by Wednesday, marking the end of the two-week heatwave. This system will bring a slight chance of light showers to the Valley on Tuesday night into Wednesday morning. Temperatures are projected to drop into the 80s by Wednesday, with the cooler trend continuing through next weekend. The National Weather Service indicates that the Valley will likely see temperatures in the 80s for the remainder of the week, providing a welcome reprieve from the recent heat. The weather shift highlights the dynamic nature of Arizona’s climate, where rapid temperature changes are common. Residents are advised to stay prepared for varying conditions, including the possibility of thunderstorms in the northern regions.#national_weather_service #arizona #federal_aviation_administration #phoenix #phoenix_sky_harbor_international_airport

US House Transportation Committee Chair Will Not Seek Re-election The chair of the House Transportation and Infrastructure Committee, Sam Graves (R-MO), has announced he will not seek re-election, according to sources cited by Reuters. This decision marks another departure from Congress as dozens of lawmakers prepare to leave their seats. Graves, a long-standing advocate for aviation policy, has played a pivotal role in shaping key legislation, including the recent passage of an aviation safety bill that received unanimous approval. His tenure also included oversight of the 2024 reauthorization of the Federal Aviation Administration, a major legislative effort aimed at modernizing air traffic management and enhancing safety protocols. Graves’ decision to step down was confirmed by his statement to the Wall Street Journal, where he expressed no intention to run for another term. The move comes amid broader shifts in the political landscape, with many members of Congress retiring or transitioning to other roles. His departure is expected to create a vacancy in a committee critical to shaping transportation policy, including infrastructure funding, environmental regulations, and aviation safety standards. The announcement was first reported by Reuters, which cited unnamed sources close to the situation. Graves’ leadership has been instrumental in advancing legislation that balances industry needs with public safety, particularly in the wake of recent aviation incidents. His absence from the committee will likely prompt a leadership transition, though the specifics of his successor remain unclear.#federal_aviation_administration #reuters #house_transportation_and_infrastructure_committee #us_house_transportation_committee #sam_graves

United 737 and US Army Black Hawk Involved in Santa Ana Close Call On the evening of Tuesday, March 24, a US Army UH-60M Black Hawk helicopter crossed in front of a United Airlines 737-800 aircraft approaching Santa Ana John Wayne Airport (SNA) in California. The incident prompted a Traffic Collision Avoidance System (TCAS) Resolution Advisory for the United crew, indicating a potential conflict between the two aircraft. The closest point of approach occurred at 03:40:35 UTC, with the helicopter at 1,425 feet altitude and the 737 descending through 2,000 feet. The vertical separation between the aircraft was 525 feet, while lateral distance measured 1,422 feet. United flight UA589, operating from San Francisco to Santa Ana, received the TCAS advisory as the helicopter intruded into its flight path. The crew immediately arrested the aircraft’s descent to comply with the advisory and continued the approach, ultimately landing safely approximately three minutes after the closest point. The incident highlights the risks of close proximity between fixed-wing aircraft and helicopters during airport operations. The Federal Aviation Administration (FAA) announced an investigation into the incident on March 26, focusing on whether the agency’s new rule prohibiting visual separation between helicopters and fixed-wing aircraft near major airports was applied. The rule, effective recently, mandates radar-based separation instead of relying on visual confirmation to prevent conflicts. The FAA’s probe aims to assess compliance with the regulation and determine if procedural lapses contributed to the near-miss. Data from the incident, including TCAS status codes, is available for download in CSV format.#federal_aviation_administration #united_airlines #us_army_black_hawk #santa_ana_john_wayne_airport #california_air_national_guard

Military Helicopter Near United Flight Sparks FAA Investigation at John Wayne Airport A military helicopter crossed in front of a United Airlines flight as the aircraft approached John Wayne Airport on Tuesday night, prompting an investigation by the Federal Aviation Administration. The incident occurred around 8:40 p.m. when United Airlines Flight 589 was descending toward the airport, according to the FAA. A Sikorsky Black Hawk helicopter reportedly entered the flight path of the commercial plane, coming within approximately 525 feet vertically and 1,422 feet horizontally at their closest point, as recorded by flight tracking website FlightRadar24. The website described the event as a “close call.” United Airlines confirmed that its pilots were alerted by air traffic control to a military helicopter near the airport during the flight’s final approach. The crew reported seeing the helicopter and received a traffic alert, prompting them to level the aircraft before safely landing about three minutes later. FlightRadar24 noted that the commercial plane avoided the helicopter and completed its descent into Santa Ana without incident. John Wayne Airport spokesperson AnnaSophia Servin told a reporter that the situation did not constitute a close call, though the FAA has launched an investigation to determine whether a recently implemented measure limiting the use of “visual separation” between aircraft and helicopters was in effect. Visual separation, a method allowing pilots to maintain distance from other aircraft by keeping them in sight rather than relying solely on radar and air traffic controllers, is now being restricted. According to Juan Browne, a former U.S.#federal_aviation_administration #united_airlines #john_wayne_airport #flight_radar24 #california_national_guard

Federal Aviation Administration Investigates Near Miss Between United Airlines Plane and Black Hawk Helicopter in California The Federal Aviation Administration is examining a close call involving a United Airlines passenger jet and a U.S. Army National Guard Black Hawk helicopter at John Wayne Airport in Santa Ana, California. The incident occurred on Tuesday evening when United Airlines Flight 589, en route from San Francisco, encountered a collision avoidance alarm while preparing to land. The warning was triggered by a UH-60 Black Hawk helicopter operating under the callsign Knife 25. According to FlightRadar24, the closest point between the aircraft was 525 feet vertically and 1,422 feet laterally. United Airlines stated that air traffic control had advised the pilots of the Boeing 737 to monitor for a military helicopter near the airport during the final approach. After the alarm activated, the pilots halted their descent and leveled off until the helicopter passed, allowing them to land safely. An air traffic controller’s audio recording, shared by LiveATC.net, included a statement: “We’re gonna be addressing that, because that was not good.” The National Guard confirmed the helicopter was on a routine training mission, returning to its base at Los Alamitos Airfield. The agency noted the aircraft followed an established Visual Flight Rules (VFR) route at an assigned altitude while communicating with air traffic control. A thorough review is underway in coordination with relevant agencies. This incident follows a similar tragedy in January 2025, when a Black Hawk helicopter collided with an American Airlines regional jet at Ronald Reagan Washington National Airport, resulting in 67 fatalities—the deadliest aviation disaster in the U.S. in nearly two decades.#federal_aviation_administration #united_airlines #black_hawk_helicopter #john_wayne_airport #national_guard

Hundreds of passengers stranded in Newark, New Jersey, USA as Newark Liberty International Airport delays 168 flights and cancels 10, disrupting major airlines and travel routes Travel plans were upended for hundreds of passengers this week as Newark Liberty International Airport (EWR) faced significant operational disruptions, with 168 flights delayed and 10 flights canceled. The chaos left travelers stranded, frustrated, and scrambling for alternate routes and accommodations. Flights to major domestic hubs, key U.S. cities, transcontinental services, and international departures were impacted, creating a ripple effect across airline networks and travel itineraries. The delays and cancellations at EWR, a major gateway for the New York metropolitan area, tested the patience of families, business travelers, and tourists, highlighting the fragility of air travel during peak seasons. Whether it was a family trying to start a much-needed vacation, a business traveler hurrying to a critical meeting, or an international visitor returning home, the sequence of disrupted flights tested the resilience of many who passed through Newark’s busy terminals. Passengers encountered shifting departure boards, long waits at gates, and the arduous task of rebooking as airline and airport staff worked to manage the chaos. The disruption at Newark Liberty International Airport saw 168 delayed departures and 10 cancellations across several major airlines and routes. Newark, which serves the New York/New Jersey region alongside John F. Kennedy International Airport and LaGuardia, is a crucial hub for carriers like United Airlines, American Airlines, and Delta Air Lines, as well as numerous international operators.#delta_air_lines #federal_aviation_administration #united_airlines #newark_liberty_international_airport #american_airlines

TSA Wait Times at Philadelphia International Airport: What Weekend Travelers Should Know Philadelphia International Airport is among the busiest in the nation, designated as a Core 30 airport by the Federal Aviation Administration. Combined with the high volume of travelers on Fridays, which are among the busiest days for air travel, understanding TSA wait times is critical for weekend flyers. As of Friday morning, March 20, the average TSA security wait time at PHL is approximately 30 minutes. Travelers with TSA PreCheck, particularly at Terminal D/E, can expect a significantly shorter wait, with the process taking around 25 minutes less than standard security lines. Those planning to depart PHL this weekend or early next week are advised to check the airport’s real-time TSA wait time website frequently for updates. It’s important to note that the Transportation Safety Administration does not offer reimbursement for missed flights caused by delays in the security screening process. However, travelers may consider purchasing third-party travel insurance to cover such expenses. Additional delays could occur due to recent terminal closures at PHL. Terminal C was shut down in early March, followed by the closure of Terminal A-West and Terminal F. These closures have increased the volume of passengers at remaining terminals, potentially lengthening wait times. The ongoing partial federal government shutdown is also affecting air travel nationwide. TSA has reported an absence rate of about 10%, which has strained staffing levels and contributed to extended security lines. Travelers are encouraged to arrive at the airport well in advance to account for these factors. (This story has been updated to correct a misspelling in a headline)#federal_aviation_administration #philadelphia_international_airport #transportation_security_administration #tsa_precheck #terminal_d_e