BFO93LA076 · Hockenbury BOWERS FLY BABY BOWERS FLY
Hockenbury BOWERS FLY BABY BOWERS FLY · Accident: partial loss of engine power (mechanical failure) en route
From Lakewood Airport (N12) to Lincoln Park Airport (N07)
Event
- NTSB case
- BFO93LA076
- 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
Hockenbury BOWERS FLY BABY BOWERS FLY
- Aircraft type
- Hockenbury BOWERS FLY BABY
- 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
- N80PH
- Operator
- Peter Hockenbury
- Onboard fatalities
- Unknown
- Route
- From Lakewood Airport (N12), LAKEWOOD ARPT, NJTo Lincoln Park Airport (N07), Lincoln Park, 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
- 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
- Partial loss of engine power (mechanical failure)
- 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
- 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
- Substantial
Cause areas
- Fuel system, carburetor › Disabled
Approximate · Estimated position: the centre of Peapack, NJ, the place the record names. Not the accident site.
NTSB narrative
WHILE AT CRUISE, THE AIRPLANE'S ENGINE LOST PARTIAL POWER. THE PILOT REPORTED THAT HE APPLIED CARBURETOR HEAT AND CHECKED THE OIL TEMPERATURE AND PRESSURE. THE ENGINE DID NOT REGAIN POWER. THE PILOT ATTEMPTED TO MAKE A FORCED LANDING IN A YARD BELOW THE AIRPLANE'S FLIGHT PATH BUT DURING THE APPROACH TO LANDING, THE AIRPLANE COLLIDED WITH TREES. THE AIRPLANE FELL TO THE GROUND AND CAME TO REST INVERTED. POST ACCIDENT EXAMINATION OF THE AIRPLANE DID NOT REVEAL ANY AIRFRAME ANOMALIES. THE ENGINE WAS DISMANTLED AND EXAMINED. EXAMINATION OF THE CARBURETOR REVEALED THAT THE THROTTLE VALVE ACTUATING ARM, WHICH WAS FASTENED TO THE THROTTLE SHAFT, WAS LOOSE AND THEREFORE WOULD NOT OPEN THE THROTTLE VALVE FULLY.
Probable cause
THE FAILURE OF THE THROTTLE VALVE ACTUATING ARM WHICH RESULTED IN PARTIAL OPENING OF THE THROTTLE VALVE. A FACTOR RELATED TO THE ACCIDENT WAS THE UNSUITABLE TERRAIN AVAILABLE FOR LANDING.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record BFO93LA076
- Event ID
- 20001211X12307
- Case number
- BFO93LA076
- 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: 0567890de44b5184f3591f3f95a6e31109cf1ac1c20c5dbe0c4bf4a402618216; retrieved 2026-09-21T22:57:45.187Z.