FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC88LA058 · Cessna 182

19 Dec 1987 · Hammonton, NJ, United States

Cessna 182 · Accident: fire while standing

From an unrecorded airport to Millville Municipal Airport (MIV)

Report a problem

Event

NTSB case
NYC88LA058
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 182

Aircraft type
Cessna 182
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
N3041Y
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo Millville Municipal Airport (MIV), Millville, NJ
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
Standing · engine(s) start-up
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
Fire
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

  • Fuel system, carburetor › Fire
  • Pilot in command › Starting procedure, improper

Approximate · Estimated position: the centre of Hammonton, NJ, the place the record names. Not the accident site.

NTSB narrative

THE AIRCRAFT HAD TAXIED TO THE RUNUP AREA AND DURING THIS PROCESS OF ENGINE RUNUP, THE PILOT STATED THAT THE ENGINE WAS RUNNING ROUGH ON ONE MAGNETO BUT SMOOTH ON THE OTHER. THE CARBURETOR MIXTURE WAS LEANED BUT THE ENGINE QUIT. WHEN AN ATTEMPT TO RESTART WAS MADE FIRE ERUPTED AND THE ACFT WAS CONSUMED BY FIRE. THE PASSENGER STATED THAT THE PLT ATTEMPTED TO RESTART 4 OR 5 TIMES. THE ACFT ENG AND CARBURETOR HAD 2400 HRS WITHOUT OVERHAUL. THIS IS BEYOND THE RECOMMENDED TIME FOR THE CARBURETOR. AVIONICS AND SAFETY INSPECTORS HAD THE OPINION THAT EXCESS FUEL PUDDLING AND BACKFIRE HAD OCCURRED DURING THE RESTART. THE CARBURETOR HAD BEEN TOO BADLY BURNED TO BE FLOW TESTED. THERE WAS NO FIRE EXTINGUISHER ON BOARD THE ACFT.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record NYC88LA058
Event ID
20001213X32777
Case number
NYC88LA058
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: ddeb18f49656628e016fb51707f69e6ca2ce90f317a248339cc2f2b5cb26a683; retrieved 2026-09-23T11:22:55.184Z.