FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC83FA171 · Stinson 108

11 Jul 1983 · Farmingdale, NY, United States

Stinson 108 · Accident: airframe, component or system failure while standing

Report a problem

Event

NTSB case
NYC83FA171
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
2 · 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

Stinson 108

Aircraft type
Stinson 108
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
N90DD
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo 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
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
Airframe, component or system failure
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, line › Failure, total
  • Fuel system, line › Fire
  • Fuel system, tank › Exploded
  • Pilot in command › Maintenance, inadequate

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

THE CARBURETOR HAD BEEN PREVIOUSLY REMOVED & REWORKED, THEN WAS REINSTALLED. AFTER THE INSTALLATION, WHICH INCLUDED A LEAK CHECK, THE PLT GOT INTO THE LEFT FRONT SEAT & THE PASSENGER/MECHANIC GOT INTO THE RIGHT FRONT SEAT. THE PLT PRIMED THE ENG, THEN MADE A START. AFTER STARTING, THE ENG RAN FOR APRX 20 SECONDS, THEN STOPPED. THE OCCUPANTS DISCUSSED THE PROBLEM & DECIDED THAT THE FUEL LINE WAS PROBABLY 'AIR BOUND.' A DECISION WAS MADE TO KEEP THE ENG RUNNING BY USING THE PRIMER. AFTER RESTARTING, THE ENG CONTINUED TO RUN, BY USE OF THE PRIMER, FOR 30 TO 40 SEC, THEN THE PLT OBSERVED A FIRE IN THE LOWER RIGHT CORNER OF THE COCKPIT. THE OCCUPANTS EVACUATED THE BURNING PLANE, BUT THE PLT FELL & THE PASSENGER RETURNED TO HELP. AT ABOUT THAT TIME, THE RIGHT WING TANK EXPLODED & BOTH OCCUPANTS WERE BURNED. AN EXAM REVEALED THAT THE MAIN FUEL LINE FROM THE GASCOLATOR TO THE CARBURETOR HAD BROKEN. THE PLT DIED TWO DAYS LATER.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record NYC83FA171
Event ID
20001214X43896
Case number
NYC83FA171
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: fe448297fdc0318e25726399e3fbd4952fd8b631c3fac27d9b9813f1e0ac564f; retrieved 2026-09-21T06:30:36.328Z.