Atlantic Coast Airlines Fairchild Dornier DO-328-300 incident
Fairchild Dornier DO-328-300 · Incident: airframe, component or system failure during initial climb
From LaGuardia Airport (LGA) to Columbia Metropolitan Airport (CAE)
Event
- NTSB case
- IAD02IA076
- 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
- Incident
- 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
Fairchild Dornier DO-328-300
- Aircraft type
- Fairchild Dornier DO-328
- 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
- N409FJ
- Operator
- Atlantic Coast Airlines
- Onboard fatalities
- Unknown
- Route
- From LaGuardia Airport (LGA), NEW YORK, NYTo Columbia Metropolitan Airport (CAE), Columbia, SC
- 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
- Initial climb
- 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
- None
Cause areas
- Reason for occurrence undetermined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The crew reported a partial loss of flight display information shortly after departure, declared an emergency, and landed uneventfully at the departure airport. This was the operator's fourth reported instance where this type of event had occurred on this make/model airplane. As a result of the investigation, no failure could be identified that would have caused the loss of flight displays. In addition, the manufacturer reviewed the design of the electrical system and could not identify a design failure.
Probable cause
The partial loss of flight display information for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD02IA076
- Event ID
- 20020906X01547
- Case number
- IAD02IA076
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- 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, damage. 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: 68da3462e65d289af83c87e06d4a84a93af214f08d0df2447857fb7223ffd767; retrieved 2026-09-18T15:59:43.197Z.