CHI98LA157 · Great Lakes 2T-1A-2
Great Lakes 2T-1A-2 · Accident: total loss of engine power (non-mechanical) en route
From 12D to an unrecorded destination
Event
- NTSB case
- CHI98LA157
- 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
Great Lakes 2T-1A-2
- Aircraft type
- Great Lakes 2
- 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
- N3803F
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 12DTo not recorded
- 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
- En route · climb to cruise
- 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 › Fuel supply, inadequate
- Pilot in command › Preflight planning/preparation, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot said that after takeoff, the airplane was in a climb at about 2,000 feet agl and 3 miles north of the airport when he began a turn to the east. During the turn, the airplane's engine began to cut in and out. The pilot said that he immediately made a turn back toward the airport, and pushed all of the engine controls forward. The engine continued to surge in and out and then finally quit. The airplane was over a lake at that time. The pilot said that he turned to parallel the shore line, and the airplane touched down in the water about 100 feet from shore. Examination of the airplane's fuel system showed less than one quart of fuel between the fuel tank and the gascolator. No other anomalies with the airplane were found.
Probable cause
the pilot's inadequate preflight of the airplane's fuel system, and fuel exhaustion, which resulted in a loss of engine power, due to an inadequate supply of fuel.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI98LA157
- Event ID
- 20001211X10016
- Case number
- CHI98LA157
- 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: 182214458be1528ab294bb38932689a31fa0ebfac0651ef9f56902e365348ac2; retrieved 2026-09-22T17:46:32.230Z.