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
TSB Reports Fatal 2023 Helicopter Accident During Maintenance Run
TSB Canada details a fatal 2023 helicopter accident at Smithers Airport caused by skipped checklists and pilot distraction. Mustang Helicopters updates safety policies.

This article is based on an official press release from the Transportation Safety Board of Canada.
On May 27, 2026, the Transportation Safety Board of Canada (TSB) released its final investigation report (A23P0040) detailing the circumstances surrounding a fatal incident that occurred three years prior. The incident, which took place on May 6, 2023, at Smithers Airport (CYYD) in British Columbia, involved an Airbus Helicopters AS 350 B3 operated by Mustang Helicopters Inc.
According to the official TSB press release and accompanying report, the accident occurred during a maintenance ground run, resulting in the death of one ground worker and serious injuries to another. The investigation highlights critical safety issues, specifically the severe dangers of procedural complacency and digital distraction in the cockpit during ground operations.
The Incident at Smithers Airport
Maintenance Ground Run Turns Fatal
The TSB report outlines that on the day of the accident, the Airbus AS 350 B3 helicopter (registration C-GUXR) was undergoing maintenance ground run operations. The specific procedure was designed to balance the tail rotor drive shaft, a highly technical task that requires the helicopter’s rotor system to be operated at nearly full RPM.
During the third maintenance ground run of the day, the aircraft suddenly entered an uncommanded and rapid rotation. At the time, two maintenance staff members were positioned on the ground near the helicopter’s left cargo door to monitor the balancing equipment. As the helicopter spun out of control, both workers attempted to evade the aircraft but were struck multiple times by the tail rotor. Tragically, one worker was fatally injured at the scene, while the other sustained serious injuries and was airlifted to a local hospital.
The TSB investigation notes that the pilot eventually managed to move the engine control to IDLE, shut off the fuel supply, and apply the rotor brake. The helicopter came to a rest after rotating approximately 540 degrees. The aircraft remained upright throughout the event, and no post-impact fire occurred.
Investigation Findings and Human Factors
Skipped Checklists and Unseen Hazards
In its analysis of the events leading up to the uncommanded rotation, the TSB identified several critical human factors and procedural deviations. Following the first maintenance run of the day, the pilot abbreviated the operator’s official checklist to expedite the process.
The pilot abbreviated the operator’s official checklist to expedite the process, viewing the task as “routine and repetitive.”
According to the TSB, this deviation meant that crucial safety steps were missed. Specifically, pressure was left in the hydraulic system, and the right anti-torque pedal remained engaged in a fully forward position. Because the checklist was skipped, this critical hazard went completely undetected prior to the third engine start.
The Role of Digital Distraction
A central finding of the TSB report is the role of digital distraction in the cockpit. Investigators found that the pilot’s attention was split between the highly sensitive maintenance operation and a cellphone, which was connected to a Bluetooth earpiece.
Because the pilot was looking down when the rapid rotation began, he was not expecting the sudden movement. The TSB concluded that his delayed response to the rotational yaw force was insufficient to stop the helicopter from spinning quickly. Investigators emphasized that the minimal time saved by skipping the official checklist was negligible and ultimately contributed to the fatal outcome.
Industry Implications and Safety Actions
Regulatory Blind Spots
The TSB report highlights a significant regulatory gap within the Canadian aviation framework. Currently, there are no Transport Canada regulations that explicitly prohibit the use of cellphones or personal electronic devices in the cockpit during operations.
The safety board has previously identified the severe risks associated with cellphone use in aviation accidents, noting that electronic devices can fatally divert a pilot’s attention from activities necessary for safe operations. The TSB presents this incident as a grim case study on the dangers of complacency during ground operations, which are often falsely perceived by crews as lower-risk than active flight.
Operator Corrective Measures
Following the tragic occurrence, Mustang Helicopters Inc. implemented several corrective safety measures aimed at preventing future incidents. According to the TSB report, the company introduced a strict new distraction policy that explicitly requires the stowing of all electronic devices during operations.
Additionally, Mustang Helicopters added a new standard operating procedure (SOP) specifically tailored for maintenance ground runs to its operations manual. The company also thoroughly revised and strengthened its hazard assessments and safety briefings for both maintenance personnel and pilots.
AirPro News analysis
We note that this tragic event underscores a critical vulnerability in modern aviation operations: the intrusion of personal electronics into safety-critical environments. While active flight operations often command a pilot’s full attention, ground operations, such as maintenance runs, can falsely appear lower-risk, inviting a dangerous level of complacency. The TSB’s findings suggest that regulatory bodies like Transport Canada may need to urgently modernize their frameworks to explicitly address digital distractions. Ensuring that the cockpit remains a sterile, focused environment, even when the aircraft is firmly on the ground, is paramount to preventing similar tragedies in the future.
Frequently Asked Questions (FAQ)
What caused the helicopter to spin during the maintenance run?
According to the TSB, the pilot skipped portions of the checklist, leaving hydraulic pressure in the system and the right anti-torque pedal in a fully forward position. When the engine was started for the third run, this caused an uncommanded and rapid rotation of the aircraft.
Why didn’t the pilot stop the rotation immediately?
The TSB investigation found that the pilot was distracted by a cellphone connected to a Bluetooth earpiece and was looking down when the rotation began. This distraction led to a delayed and insufficient reaction to the sudden yaw force.
Are pilots allowed to use cellphones in the cockpit in Canada?
The TSB report highlights that there are currently no Transport Canada regulations explicitly prohibiting the use of cellphones or personal electronic devices in the cockpit during operations, identifying this as a significant regulatory blind spot.
Sources
Photo Credit: TSB
Regulations & Safety
FAA Establishes No Drone Zones for 2026 FIFA World Cup Events
FAA announces strict no drone zones around stadiums and fan events for the 2026 FIFA World Cup with severe penalties and federal enforcement.

This article is based on an official press release from the Federal Aviation Administration (FAA).
FAA Implements Strict “No Drone Zones” for 2026 FIFA World Cup
On May 28, 2026, the Federal Aviation Administration (FAA) announced comprehensive airspace restrictions for the upcoming FIFA World Cup 2026. In a highly coordinated effort with the Department of Homeland Security (DHS), the Department of Justice (DOJ), and the Federal Bureau of Investigation (FBI), the agency is establishing strict “No Drone Zones” across the United States.
These Temporary Flight Restrictions (TFRs) will cover all stadiums hosting matches, official fan events, and team base camps. According to the official press release, the initiative is designed to ensure the safety of players, staff, and spectators by keeping unauthorized Unmanned Aircraft Systems (UAS), commonly known as drones, out of restricted airspace.
With the tournament co-hosted by the United States, Canada, and Mexico, the scale of the event is unprecedented. Federal agencies have adopted a zero-tolerance policy, warning that violators will face severe financial penalties, equipment confiscation, and potential federal criminal charges.
Airspace Restrictions and Temporary Flight Rules
The FAA’s safety plan outlines specific boundaries for the No Drone Zones during match days and official events. For all stadiums hosting World Cup matches, unauthorized drone flights are strictly prohibited within a 3-nautical-mile radius. This restriction extends vertically up to 3,000 feet above ground level.
Fan Events and Base Camps
Beyond the stadiums, the FAA is also protecting official fan events and host city locations. The no-fly zones around these gathering spaces will extend to a 1-nautical-mile radius and reach up to 1,000 feet above ground level.
The agency noted that standard airspace authorizations for commercial or experienced remote pilots will be suspended during the active TFR windows. Only aircraft explicitly authorized by air traffic control or law enforcement will be permitted to operate in these areas.
Enforcement, Interception, and Severe Penalties
To manage the massive influx of international tourists and the high-profile nature of the matches, the FAA is deploying its Drone Expedited and Targeted Enforcement Response (DETER) initiative. This program accelerates the detection, identification, and enforcement of drone violations.
“As fans from around the world gather at stadiums and fan events across the country for the FIFA World Cup, the FAA is using every available tool to protect the airspace, including stronger drone-enforcement efforts,” stated FAA Administrator Bryan Bedford in the press release.
FBI Mitigation and Financial Consequences
Local law enforcement and the FBI are legally authorized to use specialized mitigation technology to intercept unauthorized drones. According to statements from the FBI Atlanta Office, agents can detect, track, and physically move aircraft out of restricted airspace while preserving evidence for prosecution.
“Should there be the need for us to intercept a drone we have the technology for that. We do have the technology to identify drones and then locate operators,” said Aaron Hope of the FBI Atlanta Office.
The financial and legal consequences for violating these TFRs are severe. The FAA outlines civil fines up to $75,000 per violation, while criminal fines can reach up to $100,000. Additional consequences include immediate confiscation of the drone, federal criminal charges, and potential arrest.
AirPro News analysis
We note that while the FAA routinely establishes TFRs for major sporting events like the Super Bowl or the World Series, the simultaneous, multi-city nature of the 2026 FIFA World Cup requires a highly coordinated federal response spanning several weeks. The deployment of the DETER initiative and explicit warnings about FBI mitigation technology highlight a growing federal concern over unauthorized drone usage at public events. These incidents not only pose physical risks to crowds from falling equipment but also threaten to disrupt global broadcast operations. For local hobbyists, utilizing tools like the FAA’s “B4UFLY” app will be essential to avoid life-altering fines during the tournament.
Frequently Asked Questions (FAQ)
What is the penalty for flying a drone near a World Cup stadium?
Violators face civil fines up to $75,000, criminal fines up to $100,000, immediate drone confiscation, and potential federal arrest.
How large is the No Drone Zone around stadiums?
The restricted airspace covers a 3-nautical-mile radius and extends up to 3,000 feet above ground level around all host stadiums.
Are commercial drone pilots exempt from these rules?
No. According to the FAA, standard airspace authorizations are suspended during active TFR windows. Only explicitly authorized law enforcement or air traffic control-approved flights are permitted.
Sources
Photo Credit: Mercedes-Benz Stadium
Regulations & Safety
Detroit Metro Airport SUV Crash Highlights Terminal Security Gaps
A vehicle breached Detroit Metro Airport’s Evans Terminal entrance in May 2026, prompting security upgrades and no serious injuries reported.

On Friday morning, May 29, 2026, a vehicle breached the entrance of the Warren Evans Terminal at Detroit Metropolitan Wayne County Airports (DTW). According to third-party news reports, a 67-year-old man drove a black SUV through the terminal’s glass doors, causing temporary closures but resulting in no serious injuries.
The incident, which occurred between 9:30 a.m. and 10:00 a.m. local time, marks the second time in just four months that a car has crashed into a DTW terminal. Authorities quickly detained the driver, who is believed to have been experiencing a mental health crisis at the time of the crash.
Operations at the Evans Terminal were halted as emergency responders secured the scene, though normal activities resumed by late morning. The McNamara Terminal remained fully operational throughout the event, and flight schedules were largely unaffected.
Details of the Terminal Breach
The Crash and Immediate Aftermath
Based on surveillance footage reviewed by the Wayne County Airport Authority, the black SUV navigated over a curb and passed through a gap between existing cement barriers. The vehicle then shattered the glass entrance near Door 4 of the Warren Evans Terminal.
Inside the building, the sudden intrusion sparked immediate panic among travelers and staff. Witnesses described a chaotic scene with people scattering to avoid the vehicle as the driver reportedly revved the engine.
“It was a very fearful moment. You had nothing but children and you know people standing everywhere,” a witness told reporters at the scene.
Despite the frightening circumstances, casualties were remarkably light. Reports indicate that only one person, a female traveler, sustained a minor knee injury while attempting to dodge the SUV. She declined medical attention and was able to board her scheduled flight.
Suspect Apprehension and Motive
Law enforcement officers swiftly apprehended the 67-year-old driver, a resident of Metro Detroit. Police confirmed that the man was unarmed and carried no explosives, ruling out terrorism or an intent to cause mass casualties.
Authorities described the suspect as highly disoriented. According to third-party reporting, the man claimed he drove into the airport because he needed to “meet Tom Cruise and save his dad.” Officials strongly suspect the individual was undergoing a severe mental health crisis.
Airport Operations and Security Response
Minimal Disruption to Flights
Following the breach, the Evans Terminal was temporarily locked down to allow airport police, the FBI, the TSA, and local fire departments to investigate and clear the area.
Fortunately for travelers, the disruption was brief. The terminal was reopened and functioning normally between 11:00 a.m. and 11:30 a.m. local time. Furthermore, the incident did not cause any direct flight delays or cancellations, and the nearby McNamara Terminal was completely unaffected.
Infrastructure and Barricade Upgrades
The physical security of airport entrances has come under intense scrutiny following this event. The Wayne County Airport Authority announced immediate plans to deploy additional temporary barricades to reinforce terminal entryways and sidewalks.
In the longer term, officials are already in the design phase for a permanent, robust barricade system. Insights gathered from Friday’s breach will be incorporated into the final engineering plans to prevent future occurrences.
A Troubling Pattern at DTW
The January 2026 Incident
Friday’s crash is particularly alarming because it closely mirrors another event from earlier this year. On January 23, 2026, a driver in a Mercedes-Benz sedan smashed through the doors of the McNamara Terminal, eventually striking a Delta Air Lines ticket counter.
That earlier incident resulted in minor injuries to six individuals. Strikingly, the driver in the January crash was also taken into custody while reportedly suffering from a mental health emergency. Following the January breach, DTW installed temporary barriers to block 90-degree turns into the doors, but Friday’s driver managed to bypass these specific countermeasures.
AirPro News analysis
The recurrence of vehicles breaching terminal doors at a major international airport within a four-month window highlights a critical vulnerability in curbside infrastructure. While aviation Safety traditionally focuses on passenger screening and sterile areas, the “landside” perimeter remains exposed to vehicular threats.
Both the January and May 2026 incidents involved individuals in mental distress rather than coordinated attacks. However, the ease with which these vehicles bypassed existing curbside protections suggests that temporary barriers are insufficient. The rapid implementation of permanent, crash-rated bollards across all DTW terminals will be essential to restore public confidence and safeguard travelers from potentially more malicious actors in the future.
Frequently Asked Questions (FAQ)
- Were there any serious injuries in the DTW terminal crash?
No. Only one minor injury was reported when a traveler fell while avoiding the vehicle. - Did the crash affect flight schedules?
No flights were delayed or canceled as a direct result of the incident. The Evans Terminal reopened by 11:30 a.m., and the McNamara Terminal was unaffected. - Was this a terrorist attack?
Authorities have confirmed the driver was unarmed and there is no evidence of malicious intent. The suspect is believed to have been experiencing a mental health crisis.
Sources: X (formerly Twitter)
Photo Credit: X
-
Regulations & Safety7 days agoAAIB Report Details Leonardo AW139 Tail Rotor Bearing Near-Miss
-
Regulations & Safety5 days agoNTSB Urges FAA to Update Runway Condition Assessment Matrix for Heavy Rain
-
Space & Satellites4 days agoFAA Orders SpaceX Investigation After Starship Flight 12 Booster Mishap
-
Space & Satellites2 days agoBlue Origin’s New Glenn Rocket Explodes During Test at Cape Canaveral
-
Route Development5 days agoHong Kong International Airport Opens Expanded Terminal 2 for Departures
