NYC93LA029 · Cessna 195B
Cessna 195B · Accident: total loss of engine power (non-mechanical) en route
From Houlton International Airport (HUL) to an unrecorded destination
Event
- NTSB case
- NYC93LA029
- 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 195B
- Aircraft type
- Cessna 195
- 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
- N4384N
- Operator
- George W Gardner · private individual
- Onboard fatalities
- Unknown
- Route
- From Houlton International Airport (HUL), Houlton, METo 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 · 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; 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
- Destroyed
Cause areas
- Pilot in command › Aircraft preflight, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT DEPARTED WITH FUEL FOR 6 HOURS OF FLYING. DURING CRUISE FLIGHT, THE PASSENGER DISCUSSED A POSSIBLE LOW FUEL CONDITION WITH THE PILOT, DUE TO THE FUEL QUANTITY GAUGE INDICATING ONLY ONE QUARTER FULL. THE POSSIBILITY OF LOW FUEL WAS REJECTED BY THE PILOT. FUEL EXHAUSTION OCCURRED 2 HOURS AND 50 MINUTES INTO THE FLIGHT. DURING THE FORCED LANDING TO AN OPEN FIELD THE AIRPLANE STRUCK A TREE AND IMPACTED THE GROUND. POST ACCIDENT INVESTIGATION BY AN FAA INSPECTOR REVEALED WET FUEL STAINS ALONG THE RIGHT WING AND FUSELAGE OF THE AIRPLANE. FUEL SIPHONING, FROM THE RIGHT WING CAP, HAD OCCURRED ON PREVIOUS FLIGHTS, AS RECALLED BY THE PILOT AND PASSENGER.
Probable cause
THE INADEQUATE PRE-FLIGHT BY THE PILOT ENSURING FUEL CAP SECURITY. A FACTOR IN THIS ACCIDENT WAS THE PILOTS COMPLACENCY IN FUEL MANAGEMENT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC93LA029
- Event ID
- 20001211X15952
- Case number
- NYC93LA029
- 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: cfe22789dd2b7117bb886f7654e02ce4eef43af973cdac01f8e84456ccf6a558; retrieved 2026-09-21T23:05:52.116Z.