NYC92LA102 · Grumman 164A
Grumman 164A · Accident: loss of control in flight during initial climb
From Bucks Airport (00N) to an unrecorded destination
Event
- NTSB case
- NYC92LA102
- 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
Grumman 164A
- Aircraft type
- Grumman 164
- 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
- N48399
- Operator
- Joseph J. Diorio · private individual
- Onboard fatalities
- Unknown
- Route
- From Bucks Airport (00N)To 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 137: Agricultural
- 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
- Initial climb
- 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 control in flight
- 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
- Stall
- 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
- Pilot in command › Airspeed, not maintained
- Pilot in command › Altitude, not attained
- Pilot in command › Stall, inadvertent
- Pilot in command › Throttle/power control, delayed
Approximate · Estimated position: the centre of Bridgeton, NJ, the place the record names. Not the accident site.
NTSB narrative
THE AGRICULTURAL AIRPLANE ATTEMPTED A TAKEOFF FROM THE GRASS RUNWAY, BUT THE PILOT WAS UNABLE TO ATTAIN SUFFICIENT ALTITUDE TO CLEAR WIRES AT THE END OF THE RUNWAY. THE PILOT TURNED THE AIRPLANE AND WAS UNABLE TO MAINTAIN AIRSPEED AND THE AIRPLANE STALLED. THE AIRPLANE WAS WITHIN 24 POUNDS OF THE MAXIMUM ALLOWABLE GROSS WEIGHT. THE TEMPERATURE WAS REPORTED AS 90 DEGREES F AND THE WINDS WERE LIGHT. A WITNESS SAID, 'THE POWER WAS NOT AT TAKEOFF DURING THE ROLL. IT APPEARED AS IF (THE PILOT) APPLIED POWER TOO GRADUALLY. AFTER TAKEOFF, HE MADE A SHARP RIGHT TURN TO AVOID THE WIRES.'
Probable cause
THE PILOT'S IMPROPER APPLICATION OF TAKEOFF POWER WHICH RESULTED IN A LENGTHENED TAKEOFF ROLL, AND HIS SUBSEQUENT STEEP TURN TO AVOID AN OBSTACLE CAUSING THE AIRPLANE TO STALL AT A LOW ALTITUDE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC92LA102
- Event ID
- 20001211X14962
- Case number
- NYC92LA102
- 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: 9ff5cee06ace4aca961fb4026c0fc48d121725d870c22ce03bdc11ddde001cd4; retrieved 2026-09-23T03:05:02.288Z.