BFO93LA079 · Cessna 172P
Royal Karina Air Service Cessna 172P · Accident: loss of control on ground/water during landing
From an unrecorded airport to N40
Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- BFO93LA079
- 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
Cessna 172P Possible conflict
- 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
- N54833
- Operator
- Royal Karina Air Service
- Onboard fatalities
- Unknown
- Route
- From not recordedTo N40
- 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 · flare/touchdown
- 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 on ground/water
- 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 › Directional control, not maintained
- Pilot in command › Ground loop/swerve, inadvertent
- Pilot in command › Recovery from bounced landing, improper
Approximate · Estimated position: the centre of Pittstown, NJ, the place the record names. Not the accident site.
NTSB narrative
THE STUDENT PILOT WAS PRACTICING TAKEOFFS, LANDINGS, GO-AROUNDS AND EMERGENCY PROCEDURES EARLIER WITH HIS INSTRUCTOR IN PREPARATION FOR HIS SOLO FLIGHT. ACCORDING TO THE INSTRUCTOR, HIS FIRST TAKEOFF AND LANDING WERE ACCOMPLISHED SUCCESSFULLY. THE SECOND TAKEOFF RESULTED IN A GO-AROUND. HOWEVER, A WITNESS REPORTED THAT ON THE THIRD LANDING, THE AIRPLANE BOUNCED AND THE PILOT ADDED POWER TO GO-AROUND, BUT THE AIRPLANE BOUNCED A SECOND TIME AND VEERED OFF THE SIDE OF THE RUNWAY, COLLIDING WITH A PARKED AIRPLANE. ACCORDING TO THE INSTRUCTOR, THERE WAS NO MECHANICAL MALFUNCTION; HOWEVER, THE WIND HAD INCREASED TO 14 KNOTS AND A WIND GUST MAY HAVE PLAYED A ROLE IN THE ACCIDENT.
Probable cause
THE PILOT'S IMPROPER RECOVERY FROM A BOUNCED LANDING, AND HIS FAILURE TO MAINTAIN DIRECTIONAL CONTROL OF THE AIRPLANE, WHICH RESULTED IN A GROUND SWERVE. THE GUSTY WIND AND PROXIMITY OF THE PARKED AIRPLANE WERE RELATED FACTORS.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record BFO93LA079
- Event ID
- 20001211X12310
- Case number
- BFO93LA079
- 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: 6bf9970df24a9b4af8d0dc716e2056e42e71be37668ea8fd5b9b1f777b9e99ca; retrieved 2026-09-23T02:07:09.723Z.