FAA Archives - Page 2 of 12

New Mexico, United States: The U.S. National Transportation Safety Board (NTSB) has revealed that a U.S. military GPS jamming exercise was underway when a Beechcraft C90 King Air air ambulance crashed into mountainous terrain near Lincoln, New Mexico, killing all four people on board. The findings were released in a preliminary report, meaning investigators have not yet determined the probable cause or contributing factors of the accident. The accident occurred at 0015 local time on May 14, 2026, after the aircraft, registered N249CP and operated by Generations Jets under Part 135 as an air ambulance flight, departed Roswell Air Center (ROW) to Sierra Blanca Regional Airport (SRR) in Ruidoso to pick up a patient for transport to Albuquerque. The flight was crewed by two pilots and carried two flight nurses employed by Trans Aero Medical Services. The crash claimed the lives of Captain Keelan Clark, First Officer Ali Kawsara, and flight nurses Sarah Clark and Jamie Novick. According to the NTSB, GPS jamming activities conducted by the U.S. military were active over the accident area during the flight. Shortly after departure, the aircraft was cleared to 12,000 feet under instrument flight rules (IFR). At 0000:26, air traffic controllers advised the crew that the aircraft had climbed to 13,000 feet, 1,000 feet above its assigned altitude. The pilot responded that the aircraft had lost GPS capability and requested headings from air traffic control. The crew initially requested the RNAV (GPS) Runway 24 approach into Sierra Blanca Regional Airport but, after losing GPS navigation, switched to the ILS Runway 24 approach. At 0001:17, the Albuquerque Air Route Traffic Control Center (ARTCC) controller contacted the operations supervisor and requested that the military stop the GPS jamming. The aircraft continued north while controllers provided radar headings. During the same period, three other aircraft also reported GPS outages, with one crew requiring additional assistance to identify a ground-based navigation aid. At about 0005, the ARTCC operations supervisor again contacted the military to stop the jamming, after which ADS-B transmissions returned to normal. At 0008, the accident crew reported having Ruidoso in sight and requested to continue visually. Controllers cleared the aircraft for a visual approach and advised the crew they could cancel IFR after descending below 9,000 feet or after landing. The pilots acknowledged the clearance and stated they would cancel IFR "in just a couple of minutes." No further radio transmissions were received. The aircraft then turned southwest toward Sierra Blanca Regional Airport. Between the airport and the aircraft lay the Capitan Mountains, which rise to 10,201 feet. Around 0010, after being informed the aircraft was on a visual approach, the military resumed the GPS jamming exercise. The King Air began descending before briefly climbing again. The final Spidertracks data point recorded the aircraft at 9,823 feet, 150 knots ground speed, and a heading of 250 degrees. Seconds later, it struck terrain at an elevation of about 9,950 feet, approximately 730 feet east and 230 feet below the Capitan Mountains Summit Radio Facility, triggering a post-impact fire that ignited a forest fire. Investigators also found that the crew's ForeFlight weather briefing included active NOTAMs warning that military GPS jamming would affect GPS, WAAS, GBAS and ADS-B navigation over a wide area encompassing the accident flight path and altitudes. Additional NOTAMs advised that Sierra Blanca Regional Airport's automated weather observation system (AWOS) was out of service, while the weather briefing indicated no METAR or TAF was available for the destination airport. The airport's published RNAV and ILS Runway 24 approach procedures also state that the procedures are not authorized when the local altimeter setting is unavailable. The NTSB emphasized that the report is preliminary and subject to change, and that it does not determine the accident's probable cause.

Military GPS Jamming Was Underway During Fatal Air Ambulance Flight, NTSB Says

Aviation Today News Desk / August 6, 2026

New Mexico, United States: The U.S. National Transportation Safety Board (NTSB) has revealed that a U.S. military GPS jamming exercise […]

Airlines

Internal Probe Reviews Boeing 737 Seat Failures In Jeju Air Crash That Killed 179 Onboard

Aviation Today News Desk / August 3, 2026

Muan, South Korea: South Korea’s investigation into the deadly Jeju Air Flight 2216 crash has entered a new phase after

Investigation

NTSB Final Report Cites Pilot Error, Icing And FAA Failures In Fatal Bering Air Crash

Aviation Today News Desk / July 31, 2026

Alaska, United States: The US National Transportation Safety Board (NTSB) has released its final investigation report into the fatal crash

Atlanta, United States: The U.S. Federal Aviation Administration (FAA) is investigating a serious runway separation incident involving two Delta Air Lines aircraft at Hartsfield-Jackson Atlanta International Airport after the jets came into close proximity during simultaneous arrival and departure operations late on July 27. The incident involved Delta Air Lines Flight DL1568, arriving from Pittsburgh, and Delta Air Lines Flight DL2472, departing for Rochester, New York. According to the FAA and flight-tracking data, Flight 1568 was on final approach when the crew initiated a go-around after the departing aircraft had not cleared the runway environment in time. As the arriving aircraft climbed away from the runway, it came into conflict with the departing Delta jet. Both flight crews received Traffic Collision Avoidance System (TCAS) resolution advisories, prompting immediate evasive action. Air traffic controllers instructed the departing aircraft to turn and continue climbing while the arriving aircraft followed its missed-approach procedure. The crews complied with the alerts and ATC instructions, allowing both aircraft to safely regain separation. According to publicly reported flight data, the aircraft came within approximately 1,800 feet horizontally and 600 feet vertically at their closest point before increasing separation. No injuries were reported, and both flights continued safely after the event. Flight 1568 subsequently entered a holding pattern before landing safely in Atlanta, while Flight 2472 continued its scheduled flight to Rochester. Air traffic control audio reviewed by multiple media outlets captured the urgency of the event. Controllers quickly issued revised instructions after recognizing the developing conflict, while one pilot was heard expressing surprise at how close the aircraft had come. The communications indicate that both the controllers and flight crews acted promptly in response to the TCAS warnings, helping prevent a more serious incident. The FAA confirmed it is investigating the occurrence to determine the sequence of events, including runway occupancy, aircraft spacing and air traffic control actions. As of the latest update, the agency has not released preliminary findings or identified a probable cause. No damage to either aircraft has been reported, and no onboard injuries have been disclosed. The airline's operating crews followed established safety procedures, including compliance with TCAS resolution advisories and ATC instructions, allowing both flights to continue safely.

Incidents

FAA Investigates Close Call Between Two Delta Air Lines Aircraft At Atlanta Airport

Aviation Today News Desk / July 30, 2026

Atlanta, United States: The U.S. Federal Aviation Administration (FAA) is investigating a serious runway separation incident involving two Delta Air

crashed while attempting to land at the Dan Creek airstrip near McCarthy, Alaska, with federal investigators probing the fatal accident. According to the Alaska State Troopers, the crash was reported at approximately 9:30 p.m. on July 27, 2026, after a personal aircraft went down at the Dan Creek airstrip, located roughly 15 to 20 miles east of the remote community of McCarthy in the Wrangell-St. Elias Mountains. Responders reached the site aboard a state aircraft early the following morning and discovered the wreckage shortly after 6 a.m. on July 28, confirming that all three occupants had died. An initial report from the Federal Aviation Administration (FAA) identified the aircraft as a Piper PA-22-150, a four-seat, single-engine airplane operating as a personal flight. According to the FAA, the aircraft banked left while landing, impacted terrain and caught fire, resulting in a post-crash fire that destroyed the aircraft and killed the pilot and two passengers. The remains of the three occupants were recovered from the wreckage and transported to the Alaska State Medical Examiner's Office for autopsy and formal identification, Alaska State Troopers said. Family members have identified local pilot Jason Lobo and 23-year-old Anadyr Elliott as two of the three people killed in the accident. The identity of the third occupant had not been officially confirmed at the time of reporting. The National Transportation Safety Board (NTSB) has opened an investigation into the accident after being notified by Alaska State Troopers. The agency is expected to determine the circumstances and probable cause of the crash. The accident remains under investigation, and authorities have not released any additional information regarding factors that may have contributed to the crash.

Aircraft Crashes

Three Killed After Piper PA-22 Crashes During Landing Attempt At Alaska Airstrip

Aviation Today News Desk / July 30, 2026

Alaska, United States: Three people were killed after a Piper PA-22-150 crashed while attempting to land at the Dan Creek

Washington, United States: The U.S. Federal Aviation Administration (FAA) on July 27, 2026, proposed inspections of passenger seat assemblies on 453 U.S.-registered Boeing 737 MAX aircraft after receiving a report that some seats may not have been correctly installed in their floor tracks. The proposed Airworthiness Directive (AD) applies to certain Boeing 737-8, 737-9 and 737-8200 aircraft. According to the FAA, the issue involves track-mounted passenger seat assemblies whose aft fitting shear plungers may not have been correctly lowered and engaged in the seat tracks. The regulator said an incorrectly installed seat assembly could disengage from the seat tracks under increased loads, during turbulence or in an emergency landing. The FAA warned that, if the condition is not corrected, it could result in injuries to passengers or crew during an emergency landing or block an aisle and slow an evacuation. The FAA said the proposed directive would require operators to conduct a detailed inspection of the seat-track fittings on each left- and right-side track-mounted passenger seat assembly to verify that they are correctly installed. Any required corrective action would also have to be carried out. "There could be up to 69 track-mounted passenger seat assemblies on each 737 MAX plane," according to details cited in the FAA proposal. The agency estimates one work-hour for the required action per affected seat assembly, with the inspection and corrective work expected to cost operators about $85 per seat assembly. The FAA estimates the total inspection cost for U.S. operators at up to $2.66 million, while Boeing has indicated that some or all costs associated with the proposed AD may be covered under warranty. The FAA's proposed rule was prompted by Boeing Special Attention Requirements Bulletin 737-25-1927 RB, dated December 10, 2025. Boeing had previously provided guidance to operators on the issue, and the FAA is now proposing to make the required inspections and corrective actions mandatory. The agency said it had determined that the unsafe condition identified in the report is likely to exist or develop on other aircraft of the same type design. The proposal does not currently indicate that all 453 aircraft have incorrectly installed seats. Instead, the FAA is proposing inspections to determine whether the seat assemblies are correctly secured and to require corrective action where necessary. The FAA has set September 10, 2026, as the deadline for public comments on the proposed directive. The agency will consider comments before deciding whether to issue a final Airworthiness Directive. The FAA proposal itself does not identify a specific accident or injury linked to the seat installation issue. Rather, the regulator is acting on the potential safety risk posed by a seat assembly becoming disengaged from its track during high-load conditions. The development comes as the FAA continues heightened oversight of Boeing's production and quality-control processes. On July 17, 2026, the agency announced that Boeing would be allowed to resume issuing airworthiness certificates for all newly produced 737 MAX and 787 aircraft from July 20, following months of FAA review of production quality data. The latest seat-track proposal is therefore another regulatory action focused on ensuring that aircraft meet approved design and safety requirements, but it does not amount to a grounding order or an immediate suspension of 737 MAX operations.

Boeing

FAA Proposes Seat Inspections For 453 Boeing 737 MAX Jets Over Installation Issue

Aviation Today News Desk / July 28, 2026

Washington, United States: The U.S. Federal Aviation Administration (FAA) on July 27, 2026, proposed inspections of passenger seat assemblies on

United States

GAO Warns FAA Cybersecurity Gaps Could Leave US Aviation Vulnerable To Threats

Aviation Today News Desk / July 21, 2026

Washington, United States: The US Government Accountability Office (GAO) has identified significant shortcomings in the Federal Aviation Administration’s (FAA) aviation

Boeing

FAA Allows Boeing To Resume Airworthiness Certification For 737 MAX And 787 Aircraft

Aviation Today News Desk / July 20, 2026

The U.S. Federal Aviation Administration (FAA) will allow Boeing to resume issuing airworthiness certificates for all newly built 737 MAX

Kansas City, United States: An Alaska Airlines Boeing 737 MAX 9 operating a scheduled flight from Seattle to Kansas City landed safely at Kansas City International Airport (MCI) late on July 15 after the flight crew reported seeing flames from one of the aircraft's engines during the approach, prompting an Alert 3 emergency response from airport rescue and firefighting personnel. No injuries were immediately reported, and the situation was brought under control within minutes. According to FlightAware data, the aircraft departed Seattle-Tacoma International Airport at 8:31 p.m. CDT and arrived at Kansas City International Airport at 11:54 p.m., approximately five minutes ahead of schedule. The aircraft involved was a Boeing 737 MAX 9. Shortly before midnight, Kansas City Fire Department Airport Rescue and Fire Fighting (ARFF) units were dispatched after an Alert 3 was declared for the arriving Alaska Airlines flight. Emergency radio transmissions captured by Broadcastify indicated dispatchers instructed ARFF-1 and supporting units to respond immediately. Within two minutes of arriving at the gate, ARFF personnel reported that the aircraft was parked safely and that no visible fire or smoke was evident. Police officers were already at the scene as emergency crews began assessing the aircraft. A subsequent radio update on July 16 stated that the aircraft had experienced an engine fire involving the No. 2 engine, but responders found that the fire had already gone out upon arrival. According to the radio traffic, the pilot had reported seeing flames, after which the aircraft was evacuated as a precaution while firefighters investigated the situation. Responders advised that the engine fire was extinguished and that everything was under control. The emergency details were obtained from Kansas City Fire Department ARFF radio traffic recorded by Broadcastify. The Federal Aviation Administration (FAA) is expected to investigate the reported engine event, while Alaska Airlines is expected to inspect the aircraft before it returns to service.

Incidents

Alaska Airlines Lands Safely In Kansas City After Reported Mid-Air Engine Fire Scare

Aviation Today News Desk / July 17, 2026

Kansas City, United States: An Alaska Airlines Boeing 737 MAX 9 operating a scheduled flight from Seattle to Kansas City

Harrietstown, United States: Three people were killed after a twin-engine Piper Aerostar crashed into a wooded area moments after departing Adirondack Regional Airport in northern New York late Monday night, marking the third aircraft accident reported in the Adirondacks within a week and prompting an investigation by the National Transportation Safety Board (NTSB). According to the New York State Police, the aircraft involved was a 1976 Piper Aerostar, a high-performance twin-engine airplane. Preliminary information indicates the aircraft departed Adirondack Regional Airport in Harrietstown at approximately 10:36 p.m. EDT on July 13, 2026. Shortly after becoming airborne, while climbing to an estimated altitude of only 100 feet above the ground, communication with the aircraft was lost. State Police said they were notified at approximately 11:15 p.m. of a downed aircraft near Hearf's Way and State Route 186, close to the airport. A multi-agency search operation involving state troopers, local emergency responders and other agencies was immediately launched to locate the missing airplane. Search crews later located the wreckage in a heavily wooded area between McMaster Road and State Route 186, northwest of Saranac Lake. Officials said the aircraft had been destroyed by the impact and a subsequent post-crash fire, leaving little of the airplane intact. The Federal Aviation Administration (FAA) confirmed that the aircraft was carrying three people, the pilot and two passengers and that all three died in the crash. Authorities have not yet released the identities of the victims pending family notification. Flight tracking data reviewed by several media outlets showed that the aircraft had arrived in the Saranac Lake area earlier on Monday before departing again later that evening from Adirondack Regional Airport. The airplane was registered to Jasper Air LLC, a company based in Toms River, New Jersey. The FAA said the aircraft crashed under unknown circumstances, and investigators have not yet identified what caused the loss of control or why communication ceased almost immediately after takeoff. At this stage, no evidence has been released indicating whether weather, mechanical issues, pilot actions or other factors contributed to the accident. Residents living near the crash site described hearing loud noises shortly before emergency crews arrived. Speaking to local television station WPTZ, resident Jodie Wells recalled the frightening moments after the impact. "We both flew out of bed and ran outside. I could hear some bangs and loud popping. It was scary. It was loud." She added, "We have been sad and out of sorts ever since." Another resident, William Cole, said the sounds initially resembled a thunderstorm. "It definitely sounded almost identical to thunder." According to local reports, a nearby home's doorbell camera reportedly captured the sound of the crash, although authorities have not indicated whether the footage will form part of the investigation. The crash also forced authorities to temporarily close a section of the Adirondack Rail Trail between McMaster Road and Route 186, restricting access for walkers and cyclists while investigators examined the accident scene and documented the wreckage. The closure remained in effect on Tuesday as investigative work continued. The National Transportation Safety Board has assumed responsibility for the investigation, with assistance from the FAA. The agency's investigation is expected to include a review of the aircraft's maintenance history, pilot qualifications, weather conditions, airport surveillance information, communications records and any available flight tracking data before determining the probable cause of the accident. No distress call or emergency declaration has been reported, and officials have not confirmed whether the aircraft experienced any mechanical malfunction before communication was lost. The investigation remains in its early stages, and authorities have cautioned that it may take months before a probable cause is established.

Aircraft Crashes

3 Killed After Piper Aerostar Crashes Shortly After Takeoff In New York Adirondacks

Aviation Today News Desk / July 15, 2026

Update: 16th July, 2026 New York State Police have identified the victims as 70-year-old pilot Gabriel Jasper, his 33-year-old daughter

FAA