BFO93LA054 · Piper PA-28R-200
Flying Ten Piper PA-28R-200 · Accident: total loss of engine power (mechanical failure) en route
From Brookhaven Calabro Airport (HWV) to Republic Airport (FRG)
Event
- NTSB case
- BFO93LA054
- 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
Piper PA-28R-200
- Aircraft type
- Piper PA-28
- 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
- N56153
- Operator
- Flying Ten
- Onboard fatalities
- Unknown
- Route
- From Brookhaven Calabro Airport (HWV), Shirley, NYTo Republic Airport (FRG), Farmingdale, NY
- 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 · climb to 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
- Total 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
- Utility pole
- 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
- Engine assembly, valve, intake › Failure, total
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE INSTRUCTOR AND STUDENT WERE ON A RETURN FLIGHT AFTER PRACTICING SOME COMMERCIAL MANEUVERS, WHEN THERE WAS A LOSS OF ENGINE POWER DURING THE CLIMB TO CRUISE FLIGHT. ACCORDING TO THE INSTRUCTOR, WHEN THE LOSS OF POWER OCCURRED AT ABOUT 1200 FEET ABOVE THE GROUND, HE IMMEDIATELY TURNED THE AIRPLANE TO A 180 DEGREE HEADING AND COMPLETED THE EMERGENCY PROCEDURES. HE STATED THAT HE ARRIVED OVER OCEAN PARKWAY AT 100 FEET MSL AND THE AIRPLANE STRUCK THE GROUND IN A LEFT WING LOW ATTITUDE. THE AIRPLANE STRUCK A TELEPHONE POLE BEFORE COMING TO REST ON THE WEST BOUND LANE OF OCEAN PARKWAY. AN EXAMINATION OF THE ENGINE BY THE FAA REVEALED ZERO COMPRESSION IN BOTH THE NUMBER 1 AND 2 CYLINDERS. FURTHER EXAMINATION OF THE CYLINDERS REVEALED FAILURE OF THE NUMBER 1 INTAKE VALVE TIP AND DAMAGE TO THE NUMBER 2 AND 4 CYLINDERS.
Probable cause
THE LOSS OF ENGINE POWER DUE TO THE INTAKE VALVE FAILURE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record BFO93LA054
- Event ID
- 20001211X11928
- Case number
- BFO93LA054
- 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: 512b7cc30db7bb065bc0863c149925613c06b56ebf83cdf0a6e2e450c2038c45; retrieved 2026-09-23T02:14:26.276Z.