NTSB CAROL · Event
Event NYC00LA040
Registry · N521DA
FAA Aircraft Registry record.
Make / Model
CIRRUS DESIGN SR20
Year of manufacture
2023
Engine
LYCOMING IO-390-C3B6 (215 hp)
Seats / Engines
4 seats · 1 engine
Last airworthiness date
20231026
ADS-B equipped
Yes — Mode-S A68CF1
Registrant of record
UMANAH AVIATION LLC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
was the use of a defective tow bar, due to the lack of an adequate inspection by contract personnel, the airlines lack of an adequate preventative maintenance program for the tow bars, and the lack of oversight by the airline on the contract personnel who inspected the tow bar. A factor was the softer than specified shear pins used in the tow bar.
Factual narrative
On November 27, 1999, about 1030 eastern standard time, a Boeing 727-232, N521DA, operated by Delta Air Lines (DAL) as Delta Shuttle flight 1749, was substantially damaged during pushback from its gate at LaGuardia Airport (LGA), Flushing, New York. The 3 certificated pilots, a check airman, 4 flight attendants, 65 passengers, and 3 ground crew personnel were not injured. Visual meteorological conditions prevailed for the scheduled passenger/cargo flight that was destined for Ronald Reagan Washington National Airport (DCA), Washington, DC. An instrument flight rules (IFR) flight plan had been filed for the flight that was conducted under 14 CFR Part 121. The airplane was parked at gate number 3, at the Marine Air Terminal. It was being dispatched with the auxiliary power unit (APU) inoperative. The three engines were started prior to the start of the pushback. The cockpit was occupied by the captain, first officer, second officer, and a second officer check airman. According to the captain: "...A normal push-back commenced onto the company ramp. Initially, the tug pushed us straight back, and then it turned the aircraft approximately 90 degrees, tail pointing west...As the nose of the aircraft moved from left to right, simultaneously I heard 'set your brakes' from the tug driver as a 'crunching' sound emanated from the right side of the aircraft...." According to the second officer check airman: "...The backward movement [push] was then stopped, and the aircraft began a slight forward movement with the nose moving slowly to the right. Within a few seconds, the nose movement to the right accelerated, at which time the taxi director signaled to apply the brakes, and I heard the words 'Stop, Stop' several times...[the captain] immediately applied the brakes. At the same instant, a loud bang was heard emanating from the right side of the aircraft...." Similar statements were received from the first and second officers. There were three persons on the ground crew, two wing walkers, and the tug driver who was also in communication with the cockpit flight crew via the interphone. According to the tug driver: "...I pushed it back from gate #3 toward [taxiway] Alpha-Charlie and came to a full stop. I then put the tractor in reverse and began the pull-forward. While making the turn toward the yellow taxi line I heard a 'pop'. I told the captain on the headset to 'set your brakes' several times, but the aircraft was already coming at me quickly since the engines were running. I stopped the tractor hoping it would stop the plane, but the plane bent the tow bar and hit the tractor. I was not at the turn limit when the shear-pin broke." Both the left and right wing walkers reported they heard the shear pin break followed by the airplane striking the tug. The right side wing walker could see the first officer and signaled for him to set the brakes. After electrical power was brought to the airplane, the engines were shut down, and the passengers exited the airplane through the rear air-stair door. The passengers were then escorted to the terminal. The airplane was pushed back from the gate with hydraulic pressure removed from the nose wheel steering unit, and the torsion links connected. Two shear pins were installed on the tow bar to prevent nose wheel movement in excess of 78 degrees either side of center. An inspector from the Federal Aviation Administration (FAA) reported that one of the shear pins was fractured. According to the Safety Board Materials Laboratory report, examination of the shear pins revealed, evidence of a pre-existing crack in the area of failure. Hardness testing on both shear pins revealed a lower level of hardness than specified by DAL. The tow bar was forwarded to DAL Engineering Department in Atlanta, Georgia, for further examination. The examination was witnessed by an inspector from the FAA. According to a written report of the examination from DAL, the shear pin holes were elongated about 0.030 inches, and the tow bar was worn on the bottom of the head. In addition the head was loose on the tow bar. At LGA, the Delta Shuttle was not co-located with the rest of the DAL flights. The ground handling was accomplished by contract personnel, who were not rated airframe and powerplant mechanics. DAL had developed and used a daily examination form for the condition of their tow bars. According to the form from LGA, tow bar 43677 had been examined daily, and continued in service with no problems noted. The investigation revealed that DAL did not have a preventative maintenance program for the tow bars, or a program in place to train the contract personnel on the proper inspection of the tow bars, and to monitor the inspections they conducted. After the accident occurred, DAL conducted a fleet wide examination of their tow bars. According to data from the inspection, of 361 tow bars that were examined, 228 were found to have discrepancies that needed correction. After the accident, the tug driver was given a toxicological examination in accordance with the operators procedures. The examination was negative for drugs and alcohol. The readout of the digital flight data recorder (DFDR) revealed the airplane had been on a heading of about 073 degrees, and in 3 seconds shifted to a heading of about 85 degrees where it remained until loss of power to the recorder. As the airplane arrived on the new heading of about 085 degrees, the longitudinal acceleration recorded a peak of -0.16 Gs. The time of the peak G was 20 minutes and 24 seconds. Although the accident occurred during a forward tow, there was insufficient data from the DFDR to define the transition from pushback to forward tow. The cockpit voice recorder was listened to at the Safety Board Laboratory and found to contain 30 minutes of back ground noise along with some non-pertinent conversations. According to the DAL B727 manual, the APU inoperative procedure was to start engines one and three prior to pushback. According to the DAL Ramp Service Manual, the APU inoperative procedure was to start engines one and two. According to the expanded checklist for the Boeing 727, a pilot has the option of starting three engines at the gate. According to the DAL safety representative who participated in the accident, all engines were started due to the close proximity to the departure runway which would have given time for the proper warm-up of the engines. According to Boeing, each engine produces 800 pounds of thrust at idle. The minimum force necessary to keep an airplane in motion once it is rolling was 0.016 times the weight of the airplane. The brake away force to initiate movement was estimated at 1.5 times the force necessary to keep it moving. The computed takeoff weight was 142,740 pounds. The B727 was dispatched with the APU inoperative. The captain elected to start all engines prior to pushback due to a short taxi. After pushback, and during a forward tow, a shear pin on the tow bar failed, and the airplane rolled into a tug. Examination of the tow bar revealed looseness in the head, and worn holes for the shear pins. Metallurgical examination of the shear pins found pre-existing cracking and the pins were softer than specified. The pushback operation was conducted by contract personnel. The failed tow bar had been inspected daily by contract personnel with no problems noted and it continued in use. A fleet wide campaign found 63 percent of the tow bars in need of maintenance. The investigation revealed the airline did not have a preventative maintenance program for their tow bars, or a program to train the contract personnel in inspections of the tow bars, and to monitor their inspections. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1999_NYC00LA040.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 (stall, 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 2023 · Conference paper
The Value of Strong Partnerships to Build a Successful Aviation Maintenance Career Pathway Program for Transitioning Military Service Members
The aerospace industry is competing with other industries for a qualified workforce, and many of those competing industries are investing heavily in creating workforce development pipelines.
- 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…
- NASA NTRS 2026 · Conference Paper
Computational Analysis of Steady State Aerodynamics of Transonic Truss-Braced Wing Configuration in Deep Stall
This study presents a computational investigation of steady state aerodynamics of the Subsonic Ultra-Green Aircraft Research (SUGAR) Transonic Truss-Braced Wing (TTBW) configuration over a wide range …
- 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.
Browse the full corpus — academia portal ↗