BFO92FA069 · Cessna 172P
Raritan Valley Flying School Cessna 172P · Accident: in flight collision with object during landing
From 39N to an unrecorded destination
Event
- NTSB case
- BFO92FA069
- 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
Cessna 172P
- Aircraft type
- Cessna 172
- 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
- N55110
- Operator
- Raritan Valley Flying School
- Onboard fatalities
- Unknown
- Route
- From 39NTo 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
- Landing · aborted
- 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
- In flight collision with object
- 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
- Destroyed
Cause areas
- Pilot in command › Clearance, not maintained
Approximate · Estimated position: the centre of Princeton, NJ, the place the record names. Not the accident site.
NTSB narrative
THE AIRPLANE STRUCK A 50 FOOT HIGH TREE AT NIGHT, 1200 FEET BEYOND THE DEPARTURE END OF RUNWAY 28. THE AIRPLANE WAS HEADED WESTBOUND. THERE WERE NO KNOWN WITNESSES TO THE ACCIDENT. THE PILOT OF ANOTHER AIRPLANE WAS TRYING TO LAND USING RUNWAY 28, BUT WAS TWICE UNSUCCESSFUL, WHICH SHE ATTRIBUTED TO A TAILWIND, SO SHE LANDED ON THE FIRST TRY USING RUNWAY 10. AFTER HER SECOND TRY TO LAND ON RUNWAY 28, SHE NOTICED ANOTHER AIRPLANE, ALSO DOING A GO AROUND AFTER AN UNSUCCESSFUL LANDING ATTEMPT ON RUNWAY 28. SHE RADIOED THE PILOT TO ADVISE HIM TO USE RUNWAY 10, AND HE REPLIED WITH AN UNCLEAR TRANSMISSION WHICH ABRUPTLY ENDED. THE INVESTIGATION REVEALED THE PILOT HAD CONDUCTED NIGHT FLIGHT AT THIS AIRPORT FOUR TIMES BEFORE. HE HAD FOUR HOURS OF TOTAL NIGHT FLIGHT TIME. THE INVESTIGATION DID NOT REVEAL EVIDENCE OF MECHANICAL MALFUNCTION AND THE FLAPS WERE EXTENDED FIVE DEGREES. ACCORDING TO CESSNA, DURING A GO AROUND, THE FLAPS SHOULD BE REDUCED TO 10 DEGREES UNTIL OBSTACLES HAVE BEEN CLEARED.
Probable cause
THE PILOT'S FAILURE TO MAINTAIN CLEARANCE OVER AN OBSTACLE. CONTRIBUTING FACTORS WERE A TAILWIND, DARK NIGHT, AND PREMATURE RAISING OF THE FLAPS.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record BFO92FA069
- Event ID
- 20001211X14578
- Case number
- BFO92FA069
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1992-05-19.
- API snapshot SHA-256: 67ca0d08676832cbe60b917f87513712ad67928f8e5c15fcd51a8b9193878730; retrieved 2026-09-21T01:11:52.110Z.