ATL82FKG14 · Fokker DR-1
Fokker DR-1 · Accident: total loss of engine power (non-mechanical) on approach
From Hampton, GA to Hampton, GA
Event
- NTSB case
- ATL82FKG14
- 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
- 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
Fokker DR-1
- Aircraft type
- Fokker DR-1
- 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
- N1387B
- Operator
- Allen Kirst
- Onboard fatalities
- Unknown
- Route
- From Hampton, GATo Hampton, 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 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 · 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
- 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 starvation
- 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
- Fluid, fuel › Starvation
- Pilot in command › Fuel supply, misjudged
- Pilot in command › In-flight planning/decision, improper
Approximate · Estimated position: the centre of Hampton, GA, the place the record names. Not the accident site.
NTSB narrative
THE PILOT WAS ALSO THE OWNER OF THE FIXED TRI-WING, AMATEUR-BUILT AIRCRAFT. AFTER RETURNING FROM A LOCAL FLIGHT, HE ENTERED THE TRAFFIC PATTERN. HE FLEW A LARGE PATTERN TO MAINTAIN SPACING BEHIND A CESSNA 150. AFTER MAKING A LOW APPROACH, HE POSITIONED HIMSELF BEHIND THE OTHER AIRCRAFT IN ANOTHER LARGE PATTERN. WHILE DESCENDING ON FINAL APPROACH, THE ENGINE COUGHED AND THEN QUIT. THE THROTTLE WAS PUMPED, THE ENGINE RESTARTED MOMENTARILY, THEN LOST POWER AGAIN AND COULD NOT BE RESTORED. THE PILOT WAS UNABLE TO REACH THE RUNWAY. THE PLANE WAS LANDED IN AN AREA OF BRUSH AND BRIARS ABOUT 1000 FT FROM THE RUNWAY AND WAS SUBSTANTIALLY DAMAGED. AN INVESTIGATION REVEALED NO PRECRASH, MECHANICAL FAILURES. SOME FUEL WAS REMAINING IN THE FUEL TANK. HOWEVER, THE FUEL TANK WAS OF THE OWNER'S DESIGN. WITH THE AIRCRAFT IN A STRAIGHT AND LEVEL FLIGHT ATTITUDE, THERE WAS 3/4 INCH OF FUEL. BUT WHEN IT WAS TILTED TO ABOUT 10 DEGREES NOSE DOWN, THE FUEL RAN FORWARD LEAVING NO FUEL PICKUP POINT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL82FKG14
- Event ID
- 20020917X02866
- Case number
- ATL82FKG14
- 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. 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: f5c210db9a69692c9635d1baaedb77965d5865cd317a1d35f5382812d40d6a2a; retrieved 2026-09-22T03:02:48.889Z.