CHI90LA183 · Cessna 180
Cessna 180 · Accident: total loss of engine power (non-mechanical) en route
From ATIKOKAN (no airport) to 8Y8 · CRANE LAKE, MN
Event
- NTSB case
- CHI90LA183
- 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
Cessna 180
- Aircraft type
- Cessna 180
- 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
- N2134Z
- Operator
- Cleon O. Garley · private individual
- Onboard fatalities
- Unknown
- Route
- From ATIKOKAN (no airport)To 8Y8 · CRANE LAKE, MN
- 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 · 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
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE FLOAT EQUIPPED ACCIDENT AIRPLANE NOSED OVER DURING A FORCED LANDING ATTEMPT TO A CREEK, AFTER AN ENGINE FAILURE. THE PILOT STATED IN AN INTERVIEW THAT ON THE DAY BEFORE THE ACCIDENT HE HAD DEPARTED A SEAPLANE BASE WITH FULL FUEL TANKS FOR A FLIGHT TO ANOTHER LAKE. THE FOLLOWING DAY HE RETURNED TO HIS DEPARTURE POINT USING AN UNFAMILIAR ROUTE AND BECAME DISORIENTATED. THE PILOT ALSO STATED THAT HE SUSPECTED EITHER A LOOSE GAS CAP OR A FUEL LEAK AS A CAUSE OF HIS FUEL EXHAUSTION.
Probable cause
THE PILOT'S FAILURE TO PERFORM FUEL CONSUMPTION CALCULATIONS WHICH RESULTED IN FUEL EXHAUSTION AND SUBSEQUENT LOSS OF ENGINE POWER. FACTOR WAS ROUGH/UNEVEN TERRAIN.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI90LA183
- Event ID
- 20001212X23645
- Case number
- CHI90LA183
- 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: 57de28751a803dcc3cce26b2e50ea92fb1b5a4e51fe67036a0d769d66030dd2a; retrieved 2026-09-23T05:33:16.940Z.