Regulations & Safety
NTSB Report: Envoy Airlines Wrong Runway Landing at Chicago O’Hare
NTSB final report details how pilot bias and ATC oversight led Envoy Airlines flight 3936 to land on the wrong runway at Chicago O’Hare.
NTSB Final Report: “Plan Continuation Bias” Led to Envoy Airlines Wrong Runway Landing at O’Hare
The National Transportation Safety Board (NTSB) has published its final report regarding a serious incident involving an Envoy Airlines passenger jet at Chicago O’Hare International Airport (ORD). The investigation concludes that a combination of pilot error, technical mismanagement, and air traffic control (ATC) deficiencies led an Embraer 170 to land on the wrong runway on September 25, 2024.
According to the report, released on February 25, 2026, Envoy Airlines flight 3936 (ENY3936) landed safely on Runway 10L despite being cleared for and assigned to Runway 10C. While no injuries or damage occurred to the aircraft (registration N772MR), the NTSB highlights the event as a significant example of “wrong-surface landing” risks, a top safety priority for federal regulators.
The investigation identifies “plan continuation bias” and “expectation bias” as primary psychological factors that caused the flight crew to continue an unstable approach despite lacking critical instrument guidance.
Sequence of Events: Changing Plans and Cognitive Load
The NTSB investigation details a complex arrival phase where the flight crew faced a rapid series of runway assignment changes. These changes likely contributed to a high cognitive workload and “expectation bias” as the crew prepared for landing.
According to the final report, the crew prepared for four different runways in succession due to shifting weather conditions and airport operations:
- Initial Plan: Runway 27R
- First Update: Runway 9L
- Second Update: Runway 10R
- Final Assignment: Runway 10C
The NTSB noted that this sequence of changes forced the crew to repeatedly reprogram the Flight Management System (FMS) and briefing protocols, setting the stage for the errors that followed.
Technical Mismanagement in the Cockpit
Once cleared for a visual approach to Runway 10C, the crew attempted to back up their visual flight path with an Instrument Landing System (ILS) approach to ensure precision. However, the aircraft’s systems failed to “autotune” the correct ILS frequency for Runway 10C.
In an effort to correct the automation failure manually, the captain tuned the navigation radios himself. The investigation revealed a critical error in this process:
“The flight crew’s decision to continue the approach without the correct ILS frequency in the FMS [Flight Management System].”
The report states that the captain manually tuned 108.4 MHz, which was an incorrect frequency, instead of the required 108.95 MHz for Runway 10C. Furthermore, the second radio was tuned to 113.0 MHz, a VOR frequency that provided no vertical or lateral guidance for the landing. Deprived of valid instrument data to verify their alignment, the crew relied entirely on visual cues and inadvertently lined up with Runway 10L, which runs parallel to their assigned runway.
Air Traffic Control Deficiencies
While the primary error originated in the cockpit, the NTSB assigned significant weight to the failure of Air Traffic Control to intervene. The approach controller observed that Envoy flight 3936 was aligned with Runway 10L rather than the assigned 10C.
Under Federal Aviation Administration (FAA) directives, controllers are required to notify pilots immediately if they observe an aircraft aligning with a wrong surface. However, in this instance, the controller did not issue a safety alert or order a go-around. Instead, the approach controller coordinated with the tower controller responsible for Runway 10L to ensure the strip was clear, effectively allowing the error to proceed to a landing.
The NTSB described this decision as “deficient,” noting that it bypassed critical Safety layers designed to prevent collisions.
“Air traffic control’s failure to notify the flight crew that they were lined up with the incorrect runway contrary to FAA directives.”
Probable Cause and Safety Findings
The Board’s final report formally identifies the probable cause of the incident as the crew’s failure to identify the correct runway, driven by psychological biases.
“The flight crew’s misidentification of the intended landing runway, which resulted in an approach to and landing on the wrong runway due to their planned continuation bias.”
The report emphasizes “plan continuation bias”, a phenomenon where pilots continue with an original plan (landing) despite emerging cues that suggest the plan is no longer safe or valid (such as the failure to receive positive ILS guidance). The NTSB also reiterated that wrong-surface landings remain a “top 5” safety focus for the FAA, noting that while this specific incident ended without damage, similar errors have historically led to near-misses and catastrophic collisions.
AirPro News Analysis
This incident serves as a textbook example of how “Swiss Cheese” failure models manifest in modern Aviation. While the pilots made the initial errors, mis-tuning a radio and visually misidentifying a runway, the safety net that is supposed to catch these errors also failed. The ATC decision to silently accommodate the wrong runway landing rather than correct it suggests a potential normalization of deviance in busy terminal environments.
Furthermore, the “expectation bias” noted by the NTSB highlights the vulnerability of human performance during high-workload phases of flight. When runway assignments change four times in a short window, the mental model of the arrival becomes fragmented. For operators, this underscores the importance of “stopping the line”, or initiating a go-around, when automation (like the ILS autotune) behaves unexpectedly, rather than attempting manual workarounds at low altitudes.
Sources
Sources: NTSB Final Report (ID 195210)
Photo Credit: NTSB
Regulations & Safety
FAA Proposes Torque Inspection AD for 980 Airbus Helicopters
FAA NPRM targets AS350, AS355, and EC130 helicopters over a nut retainer coating flaw that risks main rotor servo-control disconnection.
This is original reporting and analysis by AirPro News.
The Federal Aviation Administration (FAA) has proposed a new airworthiness directive (AD) mandating torque inspections on the main rotor servo-controls of 980 Airbus Helicopters AS350, AS355, and EC130 aircraft registered in the United States.
Published as a Notice of Proposed Rulemaking (NPRM) on October 19, 2026, the regulatory action addresses a mechanical vulnerability where paint or protective coating on a nut retainer can cause a loss of tightening torque. If left undetected, the FAA warns this condition could lead to the disconnection of the upper ball bearing end from the main rotor (MR) servo-control. Such a failure would result in a complete loss of helicopter control.
Inspection requirements and compliance timelines
The proposed directive targets specific members of the Airbus Helicopters Ecureuil family. The affected models include the AS350B3, AS355F, AS355F1, AS355F2, AS355N, AS355NP, EC130B4, and EC130T2 helicopters. Under the FAA proposal, operators must perform an initial inspection of the nut tightening torque on the upper ball bearing end of all MR servo-controls within 165 flight hours or six months, whichever occurs first.
The NPRM also outlines strict requirements for follow-up inspections to ensure ongoing safety. Any time an MR servo-control featuring an affected part is installed or reinstalled on an aircraft, maintenance personnel must conduct a subsequent torque check. This secondary inspection must take place between two and 10 flight hours after the installation is complete.
The FAA is accepting public comments on the NPRM through December 3, 2026. Following the closure of the comment period, the agency is expected to review industry feedback and issue a final rule mandating the inspections. The current regulatory action is classified as an interim measure. Airbus Helicopters is actively developing a permanent design change to the nut retainer that will eliminate the problematic paint or protective coating entirely, which will likely prompt further regulatory updates once certified.
Tracing the servo-control vulnerability
The engineering investigation that led to the current NPRM originated with a different Airbus Helicopters product line. In 2024, the European Union Aviation Safety Agency (EASA) received reports of two separate instances where torque was lost between the upper ball bearing end and the MR servo-control on Dauphin and EC155 helicopters. In one of those documented cases, the components completely disconnected in flight.
That discovery prompted EASA to issue an AD for the Dauphin family on June 6, 2024. The FAA subsequently mirrored that action with its own directive for U.S.-registered Dauphin helicopters on July 10, 2025. Following those initial reports, Airbus Helicopters launched a broader engineering analysis to determine the root cause of the torque loss. The manufacturer concluded that the presence of paint or protective coating on the lock washer and nut retainer compromised the friction required to maintain proper tightening torque over time.
During this investigation, the manufacturer determined that the AS350, AS355, and EC130 families share this exact design vulnerability in their main rotor flight control systems. In response to these findings, Airbus Helicopters issued Alert Service Bulletins on April 1, 2026, mandating torque checks across the affected Ecureuil fleet. EASA followed up by issuing AD 2026-0132 on July 8, 2026, to mandate the inspections for European operators. The FAA publication of the NPRM on October 19, 2026, aligns U.S. regulations with the European mandates.
Market context and fleet impact
The Airbus Helicopters Ecureuil family, currently marketed under the H125 and H130 designations, represents one of the most successful light utility helicopter programs in aviation history. Airbus Helicopters has delivered more than 7,200 Ecureuil family aircraft worldwide.
The large number of affected U.S. aircraft reflects the heavy utilization of the type across the country. The AS350 and EC130 platforms are heavily utilized across the aviation industry for critical missions, including law enforcement, emergency medical services, aerial firefighting, powerline maintenance, and passenger transport. The 980 helicopters of U.S. registry represent a significant portion of the active domestic rotorcraft fleet.
AirPro News analysis
The sheer volume of U.S.-registered aircraft affected by this NPRM highlights the industry reliance on the AS350 and EC130 platforms. With 980 airframes requiring initial and recurring torque checks, maintenance providers and fleet operators will need to carefully schedule these inspections to avoid grounding critical public service assets. Because the FAA 165-hour compliance window is relatively short for high-utilization operators like air medical and police units, we expect a rapid mobilization of maintenance personnel once the final rule is published. The recurring inspection requirement for newly installed parts will also add a layer of logistical complexity for maintenance, repair, and overhaul facilities until Airbus Helicopters can field its permanent hardware redesign.
Photo Credit: Airbus
Regulations & Safety
Istanbul to Host International Aviation Law Conference on Sanctions, Drones and AI
Hudson Morgan Williams’ International Aviation Law Conference, November 5–6, 2026, features former ICAO Council President Salvatore Sciacchitano as keynote speaker and six panels ranging from arbitration to eVTOLs.
The International Aviation Law Conference will take place in Istanbul, Türkiye, on November 5–6, 2026, bringing together aviation lawyers, regulators, academics and airline and airport executives. The event opens with an invitation-only gala dinner on Thursday, November 5, followed by a full conference day at the Çırağan Palace Kempinski on Friday, November 6. The organisers expect more than 300 attendees and more than 20 speakers.
The conference is organised by Hudson Morgan Williams, a London-based law firm, which describes it as the first Aviation Law Conference in Istanbul. AirPro News is a media partner of the conference.
Six panels, from arbitration to eVTOLs
The conference day opens with a panel on the future of aviation law and the role of arbitration courts, covering aircraft lease and financing disputes, aviation insurance and liability, and contract enforcement. A second panel looks at sanctions and their impact on aviation, including leasing and finance, compliance and jurisdictional challenges. A third turns to the integration of drones into global airspace, from defence and border-security drones to unmanned traffic management and passenger drones.
After the networking lunch, Salvatore Sciacchitano gives the keynote speech at 13:50. The afternoon panels cover how AI will shape the future of aviation, including liability, insurance and regulation; how smart airports and cost-effective airlines can make aviation cheaper to operate; and urban air mobility and eVTOL aircraft, with certification, vertiport regulation, passenger rights, insurance and noise on the agenda.
The organisers note that the programme and speakers are subject to change, and the line-up for each panel has not been announced yet.
Speakers
Sciacchitano led the ICAO Council from 2020 to 2025, a period that included the adoption of the long-term goal of net-zero carbon emissions for international aviation by 2050. He previously served as Executive Secretary of the European Civil Aviation Conference (ECAC) and as Deputy Director General of ENAC, Italy’s civil aviation authority, and is now an ICAO Goodwill Ambassador.
Güliz Öztürk has been CEO of Pegasus Airlines since 2022, after serving as the airline’s Chief Commercial Officer from 2010.
Speakers listed on the conference website also include:
- Selahattin Bilgen, CEO of İGA Istanbul Airport
- Utku Coşar, independent arbitrator and Vice President of the LCIA Court
- Prof. Dr. Elmar Giemulla, professor of aviation law and attorney in Berlin and New York
- Prof. Francesca Pellegrino, Professor of Air and Space Law at the University of Messina
- Haydar Yalçın, former Deputy Director General of Türkiye’s Directorate General of Civil Aviation
- Tasman Tam, barrister in Hong Kong
- Afgan Bakhishov, Advisor to the Chairman of Azerbaijan Airlines
- Mesut Yılmaz, eVTOL Program Director at Gözen Holding
Pegasus Airlines and Corendon Airlines are among the conference’s sponsors, alongside the Turkic Arbitration Association, the International Institute of Air and Space Law at Leiden University, Özyeğin University and Studio Legale Pierallini, with Argela as a supporter.
Why Istanbul
Istanbul is the home base of Turkish Airlines and Pegasus Airlines, and İGA Istanbul Airport ranks among Europe’s busiest airports. The city will also host the Istanbul Aviation Forum on April 27–28, 2027.
How to attend
Tickets for the conference day cost €250 per attendee, and the gala dinner is by invitation only. The full programme, speaker list and registration are available on the International Aviation Law Conference 2026 website.
The conference is also listed in the AirPro News Aviation & Aerospace Events Calendar 2026–2027.
Photo Credit: Hudson Morgan Williams
Regulations & Safety
FAA Proposes Pilot Dashboard for AWOS and ASOS Outage Reports
The FAA seeks public comments on a Surface Weather Status Dashboard letting pilots report AWOS and ASOS outages directly.
The Federal Aviation Administration (FAA) is seeking public comments on a proposed Surface Weather Status Dashboard that will allow pilots and other National Airspace System (NAS) users to crowdsource reports of outages and erroneous data from automated airport weather systems.
Published in the Federal Register on October 6, 2026, the 30-day notice outlines an information collection initiative designed to improve real-time situational awareness. By integrating user-submitted trouble tickets directly into the agency’s maintenance workflow, the FAA aims to expedite repairs for critical weather infrastructure.
Streamlining weather system maintenance
The new dashboard will be hosted on the existing FAA Aviation Weather Cameras website. The agency estimates that completing a report will take a user approximately one minute, with an anticipated volume of 1,825 reports submitted annually.
Once a pilot flags an issue with an Automated Weather Observing System (AWOS) or Automated Surface Observing System (ASOS), the data will undergo verification before entering the official maintenance queue.
“It is anticipated that the information collected will be used after verification to create reports that will trigger trouble tickets within the FAA’s Remote Monitoring and Logging System (RMLS) for corrective action to be taken by the responsible parties, such as technicians within the FAA, NOAA, and non-federal entities,” the FAA stated in its filing.
The primary benefit for pilots in the air or during preflight planning is the rapid update of system status. According to the FAA, once a trouble ticket is logged in the RMLS, the Aviation Weather Cameras website will capture and display the real-time service status of the affected automated weather station within 30 minutes.
Operational impact of automated weather data
AWOS and ASOS installations are critical infrastructure for aviation safety. These automated stations provide continuous, real-time weather information, typically broadcast via radio frequency and distributed globally as Aviation Routine Weather Reports (METARs).
When these systems experience outages or transmit erroneous data, the operational impact can be severe. Pilots relying on accurate altimeter settings, visibility measurements, and cloud ceiling data may be forced to delay departures, divert to alternate airports, or cancel operations entirely.
The FAA noted that the data collected through the new dashboard will serve a dual purpose, facilitating immediate maintenance dispatch while also informing long-term infrastructure planning. The agency stated that because the collected information will be site-specific, it may be used to update future policy decisions regarding surface weather infrastructure, approvals, and audits.
Evolution of the Weather Camera Program
The integration of the Surface Weather Status Dashboard into the FAA’s weather camera portal builds on a decades-long effort to improve weather visibility for pilots. The FAA Weather Camera Program originated in 1999 in Alaska, initially designed to give pilots operating under Visual Flight Rules (VFR) actual views of current weather conditions in remote, mountainous areas where weather reporting was sparse.
Since its inception, the program has expanded to over 600 locations across the United States. The FAA credits the camera network with significantly reducing weather-related flight interruptions and accidents.
Recently, the FAA has been expanding its broader camera network by adding new locations and deploying Visual Weather Observation Systems. These newer installations combine high-resolution imagery with automated surface-weather sensors to provide a more comprehensive picture of airport conditions. The addition of the Surface Weather Status Dashboard is a congressionally mandated enhancement to this existing platform.
Regulatory timeline and next steps
The regulatory process for the dashboard began earlier in the year. On May 11, 2026, the FAA published the initial 60-day comment period notice in the Federal Register to solicit industry feedback on the concept.
The October 6, 2026, publication serves as the 30-day notice, formally requesting approval from the Office of Management and Budget (OMB) for the information collection process.
Public comments on the proposal are due by November 5, 2026. Following the close of the comment period, the FAA will seek final clearance from the OMB to implement the data collection webform and launch the dashboard to the public.
AirPro News analysis
We view the implementation of a crowdsourced reporting tool for AWOS and ASOS infrastructure as a pragmatic shift in how the FAA manages the National Airspace System. Historically, the agency has relied on automated self-reporting diagnostics or internal monitoring to detect sensor failures. However, pilots on the ground or on approach frequently identify discrepancies, such as a frozen precipitation gauge, a stuck wind direction sensor, or an uncalibrated altimeter setting, long before the system flags itself as degraded.
By formalizing a feedback loop that takes only a minute for a pilot to complete, the FAA is effectively deputizing thousands of daily airspace users as quality control inspectors. If the agency can consistently meet its stated goal of updating the public-facing service status within 30 minutes of a verified report, this dashboard will significantly reduce the latency between a localized weather system failure and the broader aviation community being alerted to the hazard.
Photo Credit: Stock – Canva
-
Defense & Military7 days agoS&K Aerospace Wins $4.3B U.S. Air Force PROS 7 Contract
-
Newsletter5 days agoAirPro News Weekly: 12 October – 19 October 2026
-
Defense & Military6 days agoUSAF Renews PTC Servigistics Contract for ESCAPE Program
-
MRO & Manufacturing7 days agoMammoth Freighters Launches 777-200LR Conversion at STAECO China
-
Space & Satellites7 days agoSpaceX CRS-35 Delivers Final iROSA Arrays to ISS