NTSB CAROL · Event
Event NYC00LA269
Aircraft involved
Probable cause & findings
The operator's loss of control of the belt-loader, due to his improper decision to depress the vehicle's accelerator in the proximity of the airplane.
Factual narrative
On September 29, 2000, at 1938 Eastern Daylight Time, a Saab 340B, N241AE, operating as American Eagle flight 4998, was substantially damaged when a baggage belt-loader collided with it, while it was parked, at General Edward Lawrence Logan International Airport (BOS), Boston, Massachusetts. There were no injuries to the 3-person crew, the 23 passengers, or the operator of the belt-loader. Visual meteorological conditions prevailed at the time of the accident. An instrument flight rules flight plan was filed for the flight, between Montreal Dorval Airport (YUL), Montreal, Quebec, and Boston. The scheduled passenger flight was conducted under 14 CFR Part 121. According to a company debrief report, when the accident occurred, the airplane was chocked, the left engine was secured, and the right engine was running. The seat belt sign had been turned off, and the passengers were standing. Witnesses reported that the belt-loader initially stopped about 10 feet from the airplane, then proceeded toward the cargo door area at a high rate of speed. The operator jumped from the loader, and the loader's vertical fin sliced through the underside of the airplane. The loader subsequently came to a stop when it impacted a lavatory cart on the other side of the airplane. The operator of the belt-loader stated that when he initially lifted the belt, he saw that it was too far from the cargo door, and decided to move the loader closer. "I sit down and pulled the stick to forward...the belt loader did not move so I pushed the accelerator and when I knew the belt loader moved very fast, I tried to get off the seat, but it was too late...." A Federal Aviation Administration (FAA) inspector reported that the loader's "dorsal fin" had cut through the fuselage for about 8 feet. Post-accident examination of the belt-loader revealed no mechanical discrepancies. The airplane was chocked, the left engine was secured, and the right engine was running. The seat belt sign had been turned off, and the passengers were standing for debarkation. A belt-loader initially stopped about 10 feet from the airplane, then proceeded toward the cargo door area at a high rate of speed. The operator jumped from the loader, and the loader's vertical fin sliced through the underside of the airplane. The operator stated that when he had tried to move the belt-loader closer, he first moved the control stick to forward. The belt loader did not move, so he pushed on the accelerator. The belt loader then proceeded quickly toward the airplane, so he jumped off. Post-accident examination of the belt-loader revealed no mechanical discrepancies. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2000_NYC00LA269.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 (loss of control). 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 2025 · Journal article (JAAER)
A Scoping Review of Aviation Loss of Control Inflight Research
Loss of control – inflight (LOC-I) contributes to aircraft accidents at unacceptably high rates. Significant industry efforts and research have aimed to improve LOC-I prevention, detection, and recove…
- SKYbrary (Eurocontrol) 2024 · SKYbrary article
Loss of Control In-Flight (LOC-I) — SKYbrary Knowledge Base
SKYbrary comprehensive knowledge-base entry on Loss of Control In-Flight — definitions, contributing factors, accident case studies (Air France 447, Colgan 3407), and prevention strategies.
- NTSB Aircraft Accident Reports 2022 · Accident report
Loss of Control on Takeoff in Icing Conditions — Citation 560XL
Cessna Citation 560XL fatal takeoff icing accident, March 2018. Investigation of a Citation 560XL loss-of-control takeoff accident in icing conditions.
- Semantic Scholar 2021 · Article (Aviation)
ANALYSIS OF GENERAL AVIATION FIXED-WING AIRCRAFT ACCIDENTS INVOLVING INFLIGHT LOSS OF CONTROL USING A STATE-BASED APPROACH
Inflight loss of control (LOC-I) is a significant cause of General Aviation (GA) fixed-wing aircraft accidents. The United States National Transportation Safety Board’s database provides a rich source…
- NASA NTRS 2021 · Presentation
Use of Design of Experiments in Determining Neural Network Architectures for Loss of Control Detection
Abstract—We describe empirical methods for selecting a neural network architecture to implement belief state inference on generic commercial transport aircraft.
- NASA NTRS 2021 · Conference Paper
Use of Design of Experiments in Determining Neural Network Architectures for Loss of Control Detection
We describe empirical methods for selecting a neural network architecture to implement belief state inference on generic commercial transport aircraft.
Browse the full corpus — academia portal ↗