BFO93LA170 · Cessna 172N
Reichard Aviation Cessna 172N · Accident: loss of control in flight on approach
From Potomac Airfield (VKX) to Tingo Maria Airport (TGI)
Event
- NTSB case
- BFO93LA170
- 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 172N
- 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
- N5347J
- Operator
- Reichard Aviation
- Onboard fatalities
- Unknown
- Route
- From Potomac Airfield (VKX), Friendly, MDTo Tingo Maria Airport (TGI)
- 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
- Approach · VFR go-around
- 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
- 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 › Aircraft control, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
ACCORDING TO THE PILOT, THE AIRPLANE PERFORMED SLUGGISHLY AS HE WAS MAKING AN APPROACH TO LAND. HE FLEW ONTO FINAL APPROACH AND NOTED THERE WAS ABOUT A 5 TO 7 KNOT CROSSWIND FROM LEFT TO RIGHT. HE SAID HE CONTINUED HIS APPROACH IN A 'SLIP' POSITION WITHOUT TRYING TO SLIP. HE SAID THAT WITH 'HANDS OFF' ON THE APPROACH, THE NOSE WAS ABOUT 10 DEGREES OFF TO THE LEFT OF THE RUNWAY. ALSO, HE SAID THAT NO AMOUNT OF RIGHT RUDDER WOULD LINE THE PLANE UP TO THE RUNWAY. AT ABOUT 40 TO 50 FEET ABOVE THE GROUND, HE DECIDED TO GO AROUND. THE PILOT STATED THAT THE AIRPLANE GAINED ABOUT 50 FEET OF ALTITUDE, THEN IT DESCENDED AND VEERED OFF TO THE RIGHT. SUBSEQUENTLY, THE AIRPLANE IMPACTED IN A MARSH AREA AND NOSED OVER. AN EXAM REVEALED THAT AN AILERON CABLE HAD SEPARATED; HOWEVER, THERE WAS EVIDENCE THAT IT HAD SEPARATED DURING IMPACT. NOT PREIMPACT PART FAILURE OR MALFUNCTION WAS FOUND.
Probable cause
FAILURE OF THE PILOT TO MAINTAIN CONTROL OF THE AIRCRAFT DURING A GO-AROUND. A FACTOR RELATED TO THE ACCIDENT WAS: THE CROSSWIND CONDITION.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record BFO93LA170
- Event ID
- 20001211X13344
- Case number
- BFO93LA170
- 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: fd134e786b4d858b571c4671cb887841da65875ca5f5e379fcd540fbbb8abc9e; retrieved 2026-09-21T22:48:44.517Z.