CEN20CA195 · Cessna 172 S
Barr Air Patrol Cessna 172 S · Accident: landing area undershoot
From Houma Terrebonne Airport (HUM) to Houma Terrebonne Airport (HUM)
Event
- NTSB case
- CEN20CA195
- 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
- Unknown
- 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 172 S
- 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
- N365CP
- Operator
- Barr Air Patrol
- Onboard fatalities
- Unknown
- Route
- From Houma Terrebonne Airport (HUM), Houma, LATo Houma Terrebonne Airport (HUM), Houma, LA
- Aircraft age
- About 19 years (built 2001)
- 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
- Defining eventThe 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
- Landing area undershoot
- 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
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The commercial pilot and passenger were returning to the airport after completing the pipeline patrol. As the airplane approached the airport, the pilot listened to the recorded weather and contacted the air traffic control tower. The reported wind was steady at 12 to 15 kts from 170°. The pilot was cleared to land on runway 18, and the pilot stated that he "set up for a short field landing in order to make the first taxiway on the right." He said that just before getting to the threshold of the runway, the wind "either quit or abruptly reduced" and the plane started to "sink" rapidly. The pilot thought he had cleared the runway threshold lights and added "a little" back pressure on the flight control yolk. The airplane's left horizontal stabilizer struck a runway threshold light resulting in substantial damage. The pilot indicated that there were no airplane mechanical malfunctions with the airplane during the flight.
Probable cause
The pilot's failure to maintain adequate clearance from a ground obstacle during landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN20CA195
- Event ID
- 20200526X14853
- Case number
- CEN20CA195
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 1ed3119cacc3202fedf5fb11d67963cf795b0d9e34d3fe5471985b211608cd7f; retrieved 2026-09-16T11:41:11.885Z.