NTSB CAROL · Event
Event NYC99LA092
Aircraft involved
Probable cause & findings
The belt-loader driver's loss of control of the vehicle, and his failure to follow published procedures for approaching the airplane with the belt-loader.
Factual narrative
On April 12, 1999, at 1926 Eastern Daylight Time, a Saab 340B, N347BE, operated as Business Express flight 6240, was substantially damaged when a baggage belt-loader sliced through a portion of the fuselage, in an area under the cargo door. The airplane had just been parked at the gate, at General Edward Lawrence Logan International Airport (BOS), Boston, Massachusetts. The two pilots, one flight attendant, and six passengers onboard were uninjured, as was the belt-loader driver. An instrument flight rules flight plan had been filed for the scheduled passenger flight, which arrived from Northern Maine Regional Airport (PQI), Presque Isle, Maine. The flight was conducted under 14 CFR Part 121. According to the captain's statement, the airplane was parked and chocked, with the engines secured, when the belt-loader struck it. The airplane's seat belt sign had been turned off, and the parking checklist had been completed. The passengers were standing, and the flight attendant was waiting for the signal to open the door. According to the airline's director of safety, the operator of the belt-loader drove the vehicle towards the airplane's cargo door area without stopping. As it approached the airplane, the driver jumped off the belt-loader, just before it impacted the fuselage. Ground support personnel checked the belt-loader braking system immediately after the collision, and found no discrepancies. According to the airline's Ground Support Manual, "Any vehicle approaching an aircraft is required to stop 50 ft. (15 m.) away. Then, it will be eased up to within 8 ft. (2 m.) and again come to a stop. From that point, the driver will carefully creep up to the aircraft. Ground equipment aircraft strikes will be prevented by using this 'Fifty 'N Eight' stop - stop - creep technique." A baggage belt-loader struck the parked airplane in an area below the cargo door. The vehicle approached the airplane without stopping, and the driver jumped off just before the collision. At the time, the airplane's engines were secured, the wheels were chocked, the seat belt sign had been turned off, and the parking checklist had been completed. The passengers were standing, and the flight attendant was waiting for the signal to open the door. Ground support personnel checked the belt-loader braking system immediately after the collision and found no discrepancies. The airline had a published procedure in place, wherein the belt-loader driver was required to stop the vehicle 50 feet prior to the airplane, and again, at least 8 feet away from the airplane. The driver was then required to approach the airplane with the belt-loader at a 'creep' speed. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1999_NYC99LA092.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 ↗