FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC88LA094 · Cessna 172

26 Feb 1988 · NORTH HANOVER, NJ, United States

Mistral Aviation Cessna 172 · Accident: loss of engine power while maneuvering

From Linden Airport (LDJ) to an unrecorded destination

Report a problem

Event

NTSB case
NYC88LA094
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 172

Aircraft type
Cessna 172
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
N738MX
Onboard fatalities
Unknown
Route
From Linden Airport (LDJ), Linden, NJTo 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
Maneuvering
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
Loss of engine power
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 › In-flight planning/decision, improper

Not plotted · Location withheld: coordinates are missing, conflicting, invalid, or have no accepted acquisition method. No substitute location has been invented.

NTSB narrative

THE ENG LOST POWER WHILE THE ACFT WAS CIRCLING AT APRX 1500 FT AGL & THE OCCUPANTS WERE ENGAGED IN AERIAL PHOTOGRAPHY. SUBSEQUENTLY, THE ACFT WAS DAMAGED DURING AN EMERGENCY LANDING IN A SWAMPY AREA. AN EXAM OF THE ACFT REVEALED THE LEFT TANK WAS EMPTY. THE RIGHT TANK HAD AN UNDETERMINED AMOUNT OF FUEL WHICH APPEARED TO BE MORE THAN USABLE FUEL; HOWEVER, THE AIRCRAFT WAS RESTING ON THE GROUND, RIGHT WING LOW. THE PILOT OPERATING HANDBOOK CONTAINED A NOTE ABOUT FLYING WITH THE SELECTOR ON BOTH. IT STATED 'UNEQUAL FUEL FLOW FROM EACH TANK MAY OCCUR IF THE WINGS ARE NOT MAINTAINED EXACTLY LEVEL. RESULTING WING HEAVINESS CAN BE ALLEVIATED GRADUALLY BY TURNING THE SELECTOR VALVE HANDLE TO THE TANK IN THE 'HEAVY' WING.' THE ACFT HAD BEEN 'TOPPED' WITH FUEL PRIOR TO THE FLT & HAD FLOWN 3.5 HRS.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record NYC88LA094
Event ID
20001213X25161
Case number
NYC88LA094
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: 482b6bf9d4fa24be6de209304bff862230c32518ad207ed6dfcd797b918a8545; retrieved 2026-09-23T10:56:20.536Z.