FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

American Airlines Flight 1813

6 Feb 2001 · Boston, MA, United States

Fokker F28 MK 0100 · Accident: on ground/water collision with object while standing

From Boston Logan International Airport (BOS) to Ronald Reagan Washington National Airport (DCA)

Report a problem

Event

NTSB case
NYC01LA077
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
Airline
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Fokker F28 MK 0100

Aircraft type
Fokker F28
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N1457B
Onboard fatalities
Unknown
Route
From Boston Logan International Airport (BOS), Boston, MATo Ronald Reagan Washington National Airport (DCA), Washington, DC
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 121: Air Carrier
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Standing · engine(s) operating
First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
On ground/water collision with object
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Flightcrew › Checklist, not followed
  • Flightcrew › Diverted attention

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

During engine start, while being pushed back, both engines went to a high power setting. The airplane pushed forward against the tow bar, sheared a pin, bent the tow bar, and struck the tug. Before engine start, maintenance personnel had conducted an automated check which included automatic movements of the control wheel and throttles. The flight crew returned to their seats while the test was being conducted. At the completion of the test, the airplane was returned to service and maintenance personnel departed the cockpit. The captain initiated the BEFORE STARTING ENGINES checklist without either pilot first completing a cockpit flow setup as required by company procedures. The checklist was then interrupted by a cockpit visitor and a non-pertinent conversation took place for 3 1/2 minutes. When the checklist was resumed, several items had been missed. As the checklist was continued, the call out THRUST LEVERS was made by the first officer, and the correct response of CLOSED was given by the captain. Push back was initiated, and the captain verbalized starting the first engine as required by the checklist. As the first engine was being started, the captain initiated another non-pertinent conversation with the first officer. The second engine was then started without verbalization as required by company checklist procedures. Although company checklist procedures made both pilots responsible for ensuring a normal start, neither pilot detected that the engines were accelerating above normal idle. According to follow-up testing, the engines accelerated to a power setting that corresponded to the last position of the throttles at the completion of the automated test by maintenance.

Probable cause

the failure of the flight crew to follow the checklist prior to engine start, and their subsequent diverted attention during engine start.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC01LA077
Event ID
20010223X00504
Case number
NYC01LA077
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 40d70a691fd10d0a099408db930927c8561f53b826e49ff956372461f1b799da; retrieved 2026-09-18T16:16:51.986Z.
  • The NTSB's operator name is blank for N1457B; the operator shown is the name the NTSB records it doing business as.