Atlantic Southeast Airlines Embraer EMB-110-P1 accident
Embraer EMB-110-P1 · Accident: airframe, component or system failure on approach
From Tri-Cities Regional TN/VA Airport (TRI) to Hartsfield Jackson Atlanta International Airport (ATL)
Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- ATL85FA168
- 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
- 0
- 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
- Charter & commuter
- 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
Embraer EMB-110-P1 Possible conflict
- Aircraft type
- Embraer EMB-110
- 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
- N903FB
- Operator
- Atlantic Southeast Airlines
- Onboard fatalities
- Unknown
- Route
- From Tri-Cities Regional TN/VA Airport (TRI), Johnson City, TNTo Hartsfield Jackson Atlanta International Airport (ATL), Atlanta, GA
- 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 135: Air Taxi & Commuter
- 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
- Approach · VFR pattern final
- 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
- Airframe, component or system failure
- 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
- Pilot in command › Brakes(emergency), not used
- Pilot in command › In-flight planning/decision, improper
- Pilot in command › Inattentive
Approximate · Estimated position: the centre of Atlanta, GA, the place the record names. Not the accident site.
NTSB narrative
THE ACFT WAS ON FINAL APCH WHEN THE CIRCUIT BREAKER CAUTION LIGHT ILLUMINATED. THE PIC FAILED TO VERIFY WHICH CB TRIPPED AND ASSUMED IT WAS THE GEAR CONTROL CB. PIC THEN ACTIVATED EMERG HYDRAULIC SYS AND MANUALLY LOWERED THE GEAR. AFTER LANDING THE HYDRAULIC SELECTOR WAS LEFT IN THE EMERG POSITION WHICH RESULTED IN THE TOE BRAKES HAVING ONLY NORMAL ACCUMULATOR PRESSURE. NORMAL ACCUMULATOR PRESSURE WAS DEPLETED AND THE ACFT COLLIDED WITH A PARKED ACFT ON THE RAMP. THE PIC FAILED TO APPLY PARKING BRAKE EVEN THOUGH THE PARKING BRAKE EMERG ECCUMULATOR HAD SUFFICIENT HYDRAULIC PRESSURE. THE INITIAL TRIPPED CB WAS FOR THE LANDING GEAR WARNING SYS AND NOT THE GEAR CONTROL.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL85FA168
- Event ID
- 20001214X36347
- Case number
- ATL85FA168
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1985-05-20.
- API snapshot SHA-256: d1dc23faee28a77a173a60417c21231bf8ecd4a8a37994ad6446b1438bcb401b; retrieved 2026-09-18T20:22:29.540Z.
- The NTSB's operator name is blank for N903FB; the operator shown is the name the NTSB records it doing business as.