NTSB CAROL · Event
Event NYC03FA039
Registry · N550NW
FAA Aircraft Registry record.
Make / Model
BOEING 757-251
Year of manufacture
2001 · 2 years old at event
Engine
P & W PW2037
Seats / Engines
178 seats · 2 engines
Last airworthiness date
20010619
ADS-B equipped
Yes — Mode-S A700AC
Registrant of record
DELTA AIR LINES INC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
Maintenance personnel failure to maintain aircraft control as a result of excessive throttle input.
Factual narrative
History of Flight On January 19, 2003, about 0715 eastern standard time, a Boeing 757-251, N550NW, was substantially damaged while parked at a gate, when it was struck by an Airbus A319 being taxied by maintenance technicians at LaGuardia Airport, Flushing, New York. Both airplanes were operated by Northwest Airlines, Inc (NWA). The certificated airline transport pilot on the Boeing was not injured. The two maintenance technicians on the Airbus, and four ground crew members sustained minor injuries. One customer service agent was seriously injured. Visual meteorological conditions prevailed, and an instrument flight rules flight plan had been filed for the flight scheduled for a 0800 departure to Minneapolis, Minnesota. The scheduled passenger flight was conducted under 14 CFR Part 121. The Boeing was parked at gate 9. The first officer was in the terminal building, while the captain was in the cockpit preparing the airplane for departure. In a written statement, the captain said he heard the sound of aircraft engines at a "higher thrust level" and observed the Airbus approaching gate 10 at a "higher than normal rate of speed." He further stated, it was immediately apparent that the Airbus would not be able to stop at a normal parking location. The Airbus struck the concrete support column of the jetway, and the left wing contacted the right side of the Boeing. The nose gear sheared off the Airbus, and the right side of the Boeing sustained a 6-foot long, 2-foot wide gash, just aft of the R1 door. During an interview, the taxi mechanic-in-charge of the Airbus, who was seated in the left seat, stated he utilized the airplane checklists. After starting the auxiliary power unit, both engines, and performing a brake check, he taxied from a maintenance area to the gate area. When he arrived in the vicinity of gate 10, he activated the parking brake and waited for ground personnel and a jetway operator to arrive. After the ground personnel arrived he released the parking brake. The airplane did not move and he advanced the throttles out of their idle detents, "a couple of inches, about halfway." The airplane began to move at a "fairly decent speed," and he realized the throttles were still out of the idle detent position. He retarded the throttles and applied brakes; however, the airplane did not slow and continued until it struck the jetway. The mechanic estimated that the airplane was about halfway down the parking line when he pulled back the throttles. During an interview, the mechanic seated in the right seat, stated he was checking the right wing clearance when the airplane began to move toward the gate. He told the taxiing mechanic to apply the brakes, and observed that the throttles were out of the idle detents. He pulled the throttles back, and the airplane struck the jetway shortly thereafter. He did not apply the brakes because the "impact happened so fast." He also did not recall feeling the sensation of braking action. Other maintenance technicians and ground support personnel stated that they heard the sound of engines spooling up, and observed the airplane moving "fast," toward the gate. The accident occurred during the hours of daylight approximately 40 degrees, 46 minutes north latitude, and 73 degrees, 52 minutes west longitude.
PERSONNEL INFORMATION
Taxi Mechanic-in-Charge The taxiing mechanic was hired by NWA on February 9, 1998. On the date of the accident, he was scheduled to work from 2330 until 0730. The taxing mechanic stated he was qualified to taxi the Boeing 727, Boeing 757, and the A319/320. He was not certain if he was current. Review of the taxiing mechanic's training records revealed that he was qualified to taxi Boeing 727 and 757 airplanes. He had received approximately 5 hours of initial A319 taxi on-the-job training (OJT). However, he had not attended an A319/A320 taxi training class and did not possess an authorization to taxi the A319. The mechanic stated that he was not certain the last time he taxied the Airbus; however, he had taxied the airplane regularly as part of his normal work duties. Taxi Assistant Mechanic The taxi assistant mechanic seated in the right seat was hired by NWA on October 26, 1991. On the date of the accident, he was scheduled to work from 2330 until 0730. Review of the taxi assistant mechanic's training records revealed he was qualified and current to taxi the A319/A320. The mechanic stated he regularly taxied the Airbus and other aircraft on a daily basis as part of his normal duties. He was also qualified to taxi McDonnell Douglas DC-9, and Boeing 757 airplanes.
FLIGHT RECORDERS
The Airbus was equipped with an Allied Signal cockpit voice recorder (CVR) and a Fairchild solid state flight data recorder (FDR), which were retained for further examination.
CVR
A CVR group was convened on January 28, 2003. The CVR group reviewed the CVR recording and prepared a transcript of the final 14 minutes.
FDR
Review of the flight data recorder for the time period surrounding the accident revealed that about 12 seconds after the parking brake was released, the thrust lever angles for both engines were increased to about 17 degrees for about 9 seconds, before they were returned to the idle position. During that time, the engines N1 and N2 speeds increased to about 71, and 85 percent, respectively. Examination of the data contained on the FDR was consistent with the airplane's air data inertial reference units (ADIRU) not being "aligned" prior to the accident, and therefore an additional 11 parameters, including ground speed were not recorded. Review of the Airbus A319/A320 Taxi and Engine Run-Up checklist, revealed that item 6 of the Aircraft Power Up checklist called for "ADIRS...Align."
TESTS AND RESEARCH
Examination of airplane's brake-steering control unit, and the electronic control units from each engine, did not reveal any evidence of a system failure, which would have contributed to the accident.
ADDITIONAL INFORMATION
Toxicology Post accident drug and alcohol testing conducted on both mechanics was negative. Ramp Examination After visually examining the ramp area, an FAA inspector stated that the area sloped upward as the terrain reached the accident and adjacent gates. The taxi mechanic-in-charge reported that he was aware that the ground was slightly inclined, and he had taxied to that particularly gate on other occasions. A NWA survey of the lead-in line to gate 10, which measured 122-feet-long, revealed a .25 percent slope. The lead-in line to gate 9 measured 162-feet-long, and contained a .77 percent slope. The taxi mechanic-in-charge reported that "ninety-eight to ninety-nine percent of the time" ground personnel were already in position to park the airplane as he arrived at the gate, and he would normally taxi without stopping. The assistant taxi mechanic stated that he had to stop and wait for ground personnel to be in position to park an airplane, about one-third of the time. NWA Taxi Policy Both mechanics reported that their was normally no discussion between mechanics regarding who should be the taxiing mechanic-in-charge. At the time of the accident, NWA mechanic taxi procedures outlined in section 02-05-03 of the General Engineering and Maintenance Manual (GEMM) required the taxi mechanic-in-charge (left seat) to be properly trained, qualified and current on the applicable fleet type. The taxi assistant (right seat) was required to be run/taxi qualified on any company fleet type. After the accident, NWA added a challenge-response protocol to the run-taxi checklist to confirm taxi qualifications. NWA run/taxi qualified personnel were also required to successfully complete a new web-based training module to remain run/taxi qualified. In addition, NWA flight operations conducted a random sampling of ground taxi information from A320 ADIRU cards that document ground speed, engine speed and thrust lever movement and have utilized the information to revise their taxi policy and training. The Boeing 757 was parked at the gate with passengers aboard when an Airbus that was being taxied struck the Boeing. The Airbus was being taxied to a gate by maintenance technicians. The taxiing mechanic reported that he activated the parking brake and waited for ground personnel and a jet way operator to arrive. After the ground personnel arrived he released the parking brake. The airplane did not move and he advanced the throttles out of their idle detents "a couple of inches, about halfway." The airplane began to move at a "fairly decent speed," and he realized the throttles were still out of the idle detent position. He pulled the throttles back and applied brakes; however, the airplane did not slow and continued until it struck the jet way. Review of the flight data recorder revealed that about 12 seconds after the parking brake was released, the thrust lever angles for both engines were increased to about 17 degrees for about 9 seconds, before they were returned to the idle position. During that time, the engines N1 and N2 speeds increased to about 71, and 85 percent, respectively. The taxiing mechanic stated he was qualified to taxi the Airbus and had taxied the airplane regularly as part of his normal work duties. Review of his training records revealed he had received approximately 5 hours of initial Airbus taxi on-the-job training. However, he did not possess an authorization to taxi the A319. Examination of airplane's brake-steering control unit, and the electronic control units from each engine, did not reveal any evidence of a system failure, which would have contributed to the accident. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2003_NYC03FA039.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (maintenance). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA)
From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- Semantic Scholar 2025 · Article (Applied Sciences)
Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
Low-Resource Automatic Speech Recognition Domain Adaptation – A Case-Study in Aviation Maintenance
With timeliness and efficiency being critical in the aviation maintenance industry, the need has been growing for smart technological solutions that optimize and streamline the different underlying ta…
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
A New Trajectory in UAV Safety: Leveraging Reinforcement Learning for Distance Maintenance Under Wind Variations
In the field of aviation, safety is a critical cornerstone, and the operation of Unmanned Aerial Vehicle (UAV) systems is deeply connected with this principle.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Just Culture in Aviation: A Metaphorical Study on Aircraft Maintenance Students
Just Culture, a sub-dimension of safety culture, has been a prominent and debated topic in aviation safety in recent years.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Performance PRISM: A Comprehensive Framework For Performance Measurement In Aircraft Maintenance
Aircraft maintenance is governed by rigorous safety requirements and high operational complexity, demanding robust performance measurement frameworks to ensure optimal maintenance practices.
Browse the full corpus — academia portal ↗