ATL98LA110 · Taylorcraft BC12-D
Taylorcraft BC12-D · Accident: forced landing
From Ormond Beach Municipal Airport (OMN) to Hattiesburg Laurel Regional Airport (PIB)
Event
- NTSB case
- ATL98LA110
- 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
Taylorcraft BC12-D
- Aircraft type
- Taylorcraft BC12
- 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
- N96175
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Ormond Beach Municipal Airport (OMN), Ormond Beach, FLTo Hattiesburg Laurel Regional Airport (PIB), Hattiesburg, MS
- 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
- 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
- Forced landing
- 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 › In-flight planning/decision, poor
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, he was 2.5 hours into a 4 hour flight when he felt an urgent need to relieve himself. The pilot stated he decided to land on a road in a cultivated field. The pilot stated after landing, he noticed a post on the left side of the road and maneuvered to miss the post. During this maneuver, the airplane became airborne, and when it touched down a second time, the landing gear collapsed. According to the FAA inspector, the pilot stated he had to relieve himself, so he decided to land on an access road because he didn't see the airport. The pilot then stated that he didn't have enough clearance on the road, and decided to land in the field. The FAA inspector also stated the field was approximately 1 to 2 miles south of Thomasville Municipal Airport. According to the FAA, the airplane touched down on the edge of the field, crossed the access road, and came to rest in another field. When crossing the road, the right main landing gear was sheared off. As the airplane continued to roll, the lower third of the rudder and two fuselage longerons were bent.
Probable cause
The pilot's poor in-flight decision to attempt a forced landing in a field 2 miles from an airport, leading to an on-ground collision with rough terrain. A factor was the pilot's physiological need.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL98LA110
- Event ID
- 20001211X10766
- Case number
- ATL98LA110
- 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: 1880f195eb3d77f3f65f0263ba22c005edf8ea24ddb4e6bf5793ef330ca3bfc3; retrieved 2026-09-22T17:10:37.653Z.