Regulations & Safety
ATSB Finds Data Entry Error Caused Safety Risk on Qantas 737 Flight
ATSB report details how a data-entry error led to a Qantas 737-800 departing Canberra overweight, highlighting system and communication failures.
ATSB Report: Data Entry Error Triggered “Cascading” Safety Risks on Qantas 737 Flight
A seemingly minor data-entry mistake by ground staff initiated a complex chain of errors that resulted in a Qantas Boeing 737-800 taking off from Canberra significantly heavier than its flight crew believed. According to a final report released by the Australian Transport Safety Bureau (ATSB) regarding the December 1, 2024 incident, the Commercial-Aircraft departed with incorrect performance calculations, creating a genuine Safety risk that was only mitigated by the pilots’ conservative decision-making.
The incident highlights the fragility of automated safety systems when human operators are under pressure. As reported by ABC News and detailed in the ATSB findings, the error caused the flight management computer to calculate takeoff speeds that were too slow for the aircraft’s actual weight, increasing the potential for a tailstrike or runway overrun.
The Trigger: A Case of Mistaken Identity
The sequence of events began when a Qantas staff member in Canberra, reportedly working under high pressure due to weather-related diversions, accessed the flight planning system. According to the ATSB report, the employee inadvertently entered the aircraft code for a Boeing 717, a smaller 125-seat jet, instead of the correct Boeing 737-800, which seats 164 passengers.
While the staff member realized the mistake and corrected the aircraft type code back to a 737, they failed to notice a critical automated consequence of the initial error. When the system briefly thought the flight was a smaller Boeing 717, it automatically “offloaded” 51 passengers (11 Business Class and 40 Economy) to align with the smaller jet’s capacity. When the code was corrected, the system did not automatically re-add these passengers.
Weight and Performance Discrepancies
Because the 51 passengers were missing from the digital manifest, the final loadsheet issued to the pilots was inaccurate. The ATSB investigation revealed the following discrepancies:
- Weight Error: The aircraft was approximately 4,291 kg (4.3 tonnes) heavier than the loadsheet indicated.
- Speed Calculation: The flight management computer calculated takeoff speeds 3–4 knots lower than required for the actual weight.
Communication Breakdowns and Missed Opportunities
The ATSB described the incident as a failure of the safety system to catch the initial slip, citing “cascading” errors that bypassed multiple layers of defense. Although the initial input was a human error, the subsequent failure to rectify it involved broken chains of communication.
According to the investigation, a Load Control Manager eventually noticed the discrepancy in the system and attempted to contact the pilots via mobile phone, but the call went unanswered. The issue was then escalated to Movement Control, who attempted to radio the crew. However, the pilots had deselected the radio to focus on pre-flight data entry, a standard procedure designed to minimize distractions in the cockpit.
In a final attempt to reach the crew, Movement Control radioed the Gate Agent to pass the urgent message. This action breached standard procedure, which requires direct liaison with the flight crew for critical load errors. Consequently, the message never reached the pilots before the aircraft began its takeoff roll.
Safety Outcome and Pilot Actions
Despite the incorrect data, the flight departed safely. The ATSB credited the pilots’ conservative approach to performance planning for preventing a more serious outcome. Rather than utilizing a shorter intersection departure or applying a “headwind credit”, which allows for higher weights or lower speeds based on wind conditions, the crew elected to use the full length of the runway.
Dr. Stuart Godley, Director of Transport Safety at the ATSB, noted the importance of these decisions in the official report:
“Fortunately, the flight crew elected to use the full length of the runway… which added an increased safety margin.”
The crew only discovered the error after the aircraft was airborne.
AirPro News Analysis: The Danger of Automation Bias
This incident serves as a textbook example of “automation surprise” or bias. When the ground staff member corrected the aircraft type from 717 back to 737, they likely assumed the computer would “undo” all associated changes, including the removal of passengers. This psychological reliance on system logic can be dangerous when software is designed to be conservative (offloading passengers to prevent overbooking) but not restorative.
Furthermore, the “high workload” environment cited in the report underscores a persistent industry challenge. When staff are saturated with tasks, in this case, managing weather diversions, their ability to cross-check automated outputs diminishes. The failure here was not just individual, but systemic, as the software provided no clear warning that the passenger count had been drastically altered following the code correction.
Qantas Response and Procedural Changes
Qantas has acknowledged the findings and accepted the ATSB’s conclusions. In response to the incident, the Airlines has implemented new safety protocols to prevent recurrence. According to the report, airport staff are now required to conduct a manual headcount whenever passenger numbers in the system do not match expected figures, ensuring physical verification before a flight is closed.
Dr. Godley emphasized the broader lesson for the Aviation industry:
“The occurrence demonstrated how a small error can cascade when unusual situations are not proactively identified, addressed, or escalated by those involved in a safety system.”
Frequently Asked Questions
Was the flight ever in immediate danger of crashing?
While the risk was elevated due to incorrect speeds, the ATSB noted that the pilots’ decision to use the full runway length provided a sufficient safety buffer. Had they used a shorter intersection or less conservative settings, the risk of a tailstrike or runway overrun would have been significantly higher.
How common are data-entry errors in aviation?
Data-entry errors are a known hazard. Similar incidents have occurred in the past, including a 2014 Qantas flight where children were assigned adult weights, and a 2009 Emirates incident in Melbourne where an incorrect weight entry led to a severe tailstrike.
What happened to the staff member involved?
The report focuses on systemic improvements rather than individual punishment. It highlights that the staff member was working under high pressure due to weather disruptions, which is a known human factor in safety incidents.
Sources
Photo Credit: A Periam Photography – Shutterstock
Regulations & Safety
NTSB Preliminary Report: Ryanair 737-800 Engine Failure
NTSB confirms fan-blade-out on Ryanair 737-800 shattered cabin window, partially ejecting a passenger during climb from Thessaloniki.
This is a developing story. Information may change as official details are released.
This is original reporting and analysis by AirPro News.
On August 13, 2026, the National Transportation Safety Board (NTSB) issued its preliminary report on a July 10 uncontained engine failure aboard a Ryanair Boeing 737-800, confirming that a fan-blade-out event shattered a cabin window and caused a rapid decompression. The incident resulted in a 61-year-old male passenger being partially pulled through the shattered window before being secured by fellow passengers.
The event occurred during climb out from Thessaloniki International Airport (SKG) in Greece. The flight, operated by Ryanair subsidiary Malta Air, was bound for Memmingen, Germany (FMM). The NTSB is currently investigating potential similarities between this event and a fatal 2018 engine failure, while the agency has also publicly addressed premature speculation regarding the cause by Ryanair leadership.
Flight 1879 rapid decompression
According to the NTSB preliminary report, the Boeing 737-800 was climbing when the right-hand CFM56-7B engine experienced a fan-blade-out event. Debris from the engine struck the fuselage and shattered a window at row 11. The resulting rapid decompression pulled a passenger partially outside the aircraft. The passenger sustained neck and shoulder injuries as well as friction burns, but no fatalities occurred.
Reporting by The Air Current indicates the failure happened at an altitude of approximately 15,000 feet. Passengers described a sudden and violent disruption to the flight. A passenger told AP News that the cabin was quiet before a loud noise resembling a bursting tire occurred, adding that they knew immediately the aircraft had lost pressure due to the sudden loss of altitude.
Initial reports following the July 10 incident suggested the failure occurred in the airspace of the Republic of North Macedonia. However, flight path analysis confirmed the event took place in Greek airspace. The Hellenic Air and Rail Safety Investigation Authority officially delegated the investigation to the NTSB on July 16, 2026.
Maintenance history and preliminary findings
The NTSB preliminary report notes that bird remains were found inside the damaged engine. Flight crews had reported four suspected bird strikes to the aircraft’s number two engine in the 12 months preceding the accident. The report states that bird remains were found in two of those previous cases.
Maintenance records indicate that the fan blades on the failed right engine underwent ultrasonic inspections in November 2025 and May 2026. No damage was found during either inspection. The official cause of the July 10 failure remains under investigation by the NTSB, with participation from the Federal Aviation Administration (FAA), Boeing, and CFM International, a joint venture between GE Aerospace and Safran.
Regulatory protocols and historical precedent
The investigation has generated friction between the NTSB and Ryanair regarding public communications. On August 7, 2026, NTSB Chair Jennifer Homendy issued a letter to Ryanair CEO Michael O’Leary after he told investors the investigation was focused on foreign object damage rather than aircraft age or maintenance. Homendy stated that the NTSB had made no such determination and noted that O’Leary’s comments violated International Civil Aviation Organization (ICAO) Annex 13 protocols governing accident investigations.
The aviation industry is closely monitoring the investigation due to the aircraft and engine types involved. The Air Current reported that the event closely mirrors the April 2018 Southwest Airlines flight 1380 uncontained engine failure, which also involved a Boeing 737-700 and a CFM56-7B engine. That incident resulted in one passenger fatality after a shattered window caused partial ejection, leading the FAA to mandate engine inlet redesigns by July 2028.
The NTSB addressed the historical context directly in its preliminary report:
The investigative team is aware of previous … events with similar engine models that resulted in damage to engine inlets or cowlings and fuselage structures. Determination of any relevant similarities or details between this accident and previous events remains under investigation.
AirPro News analysis
We observe that the public rebuke of a major airline CEO by the NTSB is a rare and significant enforcement of ICAO Annex 13 communication protocols. Operators typically defer entirely to the investigating authority to avoid compromising the integrity of an active probe. The NTSB’s swift correction underscores the agency’s zero-tolerance policy for operator speculation, particularly when an event involves high-profile safety concerns like uncontained engine failures.
The CFM56-7B is one of the most widely used commercial aviation engines in the world. Any investigation involving a fan-blade-out event on this powerplant will naturally draw intense regulatory scrutiny, especially given the precedent set by the 2018 Southwest Airlines accident. While the discovery of bird remains introduces foreign object damage as a variable, we expect investigators will rigorously examine the efficacy of the ultrasonic inspections conducted in November 2025 and May 2026 to understand how the blade failure propagated.
Sources: National Transportation Safety Board
Photo Credit: NTSB
Regulations & Safety
FAA Installs New Surface Radar at Newark Airport
The FAA unveiled a new SMR-4 radar at Newark Liberty as part of a $30 million infrastructure upgrade targeting runway safety.
U.S. Transportation Secretary Sean P. Duffy and Federal Aviation Administration (FAA) Administrator Bryan Bedford unveiled a new Surface Movement Radar-Systems Model 4 (SMR-4) at Newark Liberty International Airport (EWR) on August 11, 2026, replacing a 30-year-old legacy system.
The installation is part of a broader $30 million infrastructure upgrade at the New Jersey hub designed to prevent runway incursions and reduce delays. According to the FAA press release, the SMR-4 allows air traffic controllers to track aircraft and ground vehicles across runways and taxiways in all weather and visibility conditions.
Newark’s infrastructure modernization
The $30 million funding allocation for EWR spans a three-year period and targets critical technological vulnerabilities. During the summer of 2025, the Airports experienced severe delays that prompted the FAA to deploy Software patches, expedite fiber deployment, and rebalance flight volumes. To date, 90% of the airport’s legacy copper wiring has been replaced with high-speed fiber.
“Since the start of this administration, we have been working towards building a modern system that will serve America’s skies for generations,” Duffy stated. “From replacing Newark’s ancient copper wire to investing $30 million into new infrastructure and bringing new radar online, we are delivering real safety and efficiency enhancements at one of our nation’s busiest airports.”
The FAA has set a target deadline of summer 2027 for EWR to install new electronic information displays, upgraded voice switches, and a new long-range radar system.
National surface awareness rollout
The EWR installation is one of five SMR-4 systems deployed nationwide to date. The agency has accelerated its broader technological overhaul over the past year, replacing 60% of all copper wires in its national network and converting 363 radio sites. The FAA also transitioned 19 air traffic control towers to electronic flight strips and installed 151 IP voice switches at control towers across the country.
Bedford emphasized the operational volume driving the upgrades. “Newark sees well-over a thousand flights per day, and the new Surface Movement Radar will help controllers keep those flights safe at this major U.S. hub,” Bedford said, describing the deployment as a step toward modernizing the national airspace.
The push for enhanced surface surveillance follows a fatal runway incursion at LaGuardia Airport (LGA) on March 22, 2026. In that event, Air Canada (AC) Express Flight 8646, operated by Jazz Aviation using a Bombardier CRJ900, collided with an airport firefighting vehicle on Runway 4. The National Transportation Safety Board (NTSB) confirmed two pilot fatalities and 39 injuries. The NTSB is leading the ongoing Investigation, and no official cause has been determined.
In response to surface safety concerns, the FAA has installed 96 new Surface Awareness Initiative systems nationwide over the past year to provide controllers with better situational awareness.
AirPro News analysis
The FAA’s rapid deployment of 96 Surface Awareness Initiative systems and the ongoing SMR-4 rollout represent a tangible shift toward proactive technological intervention in ground operations. While the NTSB has not yet concluded its investigation into the March 2026 LaGuardia runway incursion, the agency’s aggressive timeline for replacing legacy copper wiring and installing surface tracking tools indicates that regulators are prioritizing immediate situational awareness upgrades for air traffic controllers. We view the $30 million targeted investment at EWR as a template the FAA is likely to replicate at other high-density hubs where legacy infrastructure limits operational capacity during low-visibility conditions.
Sources: Federal Aviation Administration
Photo Credit: Federal Aviation Administration
Regulations & Safety
FAA Revises Takeoff Obstacle Notes in Terminal Procedures
The FAA updates its Terminal Procedures Publication to simplify IFR departure planning with new DER crossing altitudes.
The Federal Aviation Administration (FAA) is revising the presentation of takeoff obstacle notes within its Terminal Procedures Publication (TPP), offering pilots a simplified method to utilize standard climb gradients during Instrument Flight Rules (IFR) departures.
In a press release issued on August 5, 2026, the National Business Aviation Association (NBAA) announced the charting updates. The revisions provide pilots with a specific Departure End of Runway (DER) crossing altitude, allowing them to safely clear low, close-in obstacles without calculating non-standard climb requirements for every individual threat.
Restructuring Obstacle Departure Procedures
Under the updated format, the FAA separates “Takeoff Minimums Obstacles” from “Low, Close-in Obstacles.” The agency defines low, close-in obstacles as those measuring 200 feet or less above the DER elevation.
Previously, pilots faced complex lists of individual obstacles during pre-flight planning. The new charting method consolidates these threats into distance groupings measured in quarter-mile increments from the DER. If a pilot meets the newly published DER crossing altitude, they can proceed using the standard IFR climb gradient of 200 feet per nautical mile (ft/NM) rather than a higher, non-standard gradient.
Industry advocacy and implementation timeline
The NBAA initially launched the effort to address the complexity of takeoff obstacle notes in 2015 during the FAA Aeronautical Charting Meeting. The resulting changes stem from collaboration between the FAA, the U.S. Instrument Flight Procedure Panel, and commercial charting providers including Jeppesen and Garmin.
While the FAA has officially adopted the new presentation standards, updating the entire National Airspace System will require a phased approach. The NBAA noted that the transition across all published procedures and commercial charts will take several years to complete.
AirPro News analysis
We view this charting revision as a practical step toward reducing pilot workload during IFR departure planning. By providing a clear DER crossing altitude that validates a standard 200 ft/NM climb, the FAA removes the ambiguity of evaluating multiple low, close-in obstacles individually. This change will be particularly beneficial for operators of aircraft with limited climb performance, allowing them to determine immediately if reported weather conditions permit visual obstacle avoidance when a higher climb gradient is unachievable.
Photo Credit: NBAA
-
Defense & Military5 days agoJoby Aviation Acquires Resonant Sciences for $500 Million
-
Technology & Innovation5 days agoHyde County EMS Deploys eVTOL for Live 911 Response
-
MRO & Manufacturing2 days agoSpirit Airlines Fleet Stripped as GTF Engine Values Surge
-
Defense & Military6 days agoRheinmetall and Boeing to Build MQ-28 Ghost Bat Hub in Germany
-
Regulations & Safety3 days agoNTSB Preliminary Report: Ryanair 737-800 Engine Failure