ATL06LA022 · Embraer EMB-110P1
Embraer EMB-110P1 · Accident: total loss of engine power (non-mechanical) on approach
From Savannah Hilton Head International Airport (SAV) to Columbia Metropolitan Airport (CAE)
Event
- NTSB case
- ATL06LA022
- 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
- General aviation
- 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-110P1
- 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
- N790RA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Savannah Hilton Head International Airport (SAV), Savannah, GATo 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 91: General Aviation
- 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
- 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
- Total loss of engine power (non-mechanical)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Fuel exhaustion; Tree(s)
- 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 › Aircraft preflight, inadequate
- Pilot in command › Refueling, not performed
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot had flown the airplane the day before the accident and after landing on the morning of the accident; she ordered fuel for the airplane. While exiting the airplane another pilot informed her that he had heard a "popping noise" coming from one of the engines. The pilot of the accident airplane elected to taxi to a run up area to conduct an engine run up. The fuel truck arrived at the run up area and the pilot elected not to refuel the airplane at that time and continued the run up. No anomalies were noted during the run up and the airplane was taxied back to the ramp and parked. The pilot arrived back at the airport later on the day of the accident and did not re-order fuel for the airplane nor did she recall checking the fuel tanks during the preflight inspection of the airplane. The pilot departed and was in cruise flight when she noticed the fuel light on the annunciator panel flickering. The pilot checked the fuel gauges and observed less than 100 pounds of fuel per-side indicated. The pilot declared low fuel with Columbia Approach Control controllers and requested to divert to the nearest airport, Orangeburg Municipal. The controller cleared the pilot for a visual approach to the airport and as she turned the airplane for final, the left engine lost power followed by the right engine. The pilot made a forced landing into the trees about 1/4 mile from the approach end of runway 36. The pilot exited the airplane and telephoned 911 emergency operators on her cell phone. The pilot stated she did not experience any mechanical problems with the airplane before the accident. Examination of the airplane by an FAA inspector revealed the fuel tanks were not ruptured and no fuel was present in the fuel tanks.
Probable cause
The pilot's inadequate preflight inspection and her failure to refuel the airplane which resulted in total loss of engine power due to fuel exhaustion, and subsequent in-flight collision with trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL06LA022
- Event ID
- 20051223X02004
- Case number
- ATL06LA022
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2005-12-10.
- API snapshot SHA-256: 686fb5b4a10d62bb90468a225ba1b20ce32ae97739c0f64b055fb29a434694c5; retrieved 2026-09-21T09:01:24.464Z.