DEN90DTG01 · Adams BOREDOM FIGHTER BOREDOM FI
Adams BOREDOM FIGHTER BOREDOM FI · Accident: total loss of engine power (non-mechanical) on approach
From Devils Lake Regional Airport (DVL) to Hector International Airport (FAR)
Event
- NTSB case
- DEN90DTG01
- 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
Adams BOREDOM FIGHTER BOREDOM FI
- Aircraft type
- Adams BOREDOM FIGHTER
- 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
- N317MA
- Operator
- Adams, Steven J. · private individual
- Onboard fatalities
- Unknown
- Route
- From Devils Lake Regional Airport (DVL), Devils Lake, NDTo Hector International Airport (FAR), Fargo, ND
- 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
- 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 › Exhaustion
- Pilot in command › Planning/decision, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DUE TO AN UNEXPECTED HEADWIND THE AIRPLANE WAS RUNNING LOW ON FUEL AND THE PILOT ELECTED TO LAND SHORT OF HIS INTENDED DESTINATION. DURING APPROACH FUEL EXHAUSTION RESULTED IN A TOTAL POWER LOSS. THE PILOT MADE A FORCED LANDING IN A DITCH ON THE DOWNWIND SIDE OF A ROAD. THE PILOT LISTED AS SAFETY RECOMMENDATIONS 'BETTER FUEL PLANNING AND BETTER FLIGHT PLANNING.'
Probable cause
A POWER LOSS DUE TO FUEL EXAHUSTION AND THE PILOT'S INADEQUATE FUEL PLANNING. A FACTOR WAS THE DITCH IN WHICH TOUCHDOWN OCCURRED.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN90DTG01
- Event ID
- 20001212X23121
- Case number
- DEN90DTG01
- 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: 1abdef82e3dd83b850dfe27f3c7e3cc64501f0dbbaec26e3f71324fa0d201228; retrieved 2026-09-23T06:15:06.048Z.