FTW02LA246 · Cessna 182-Q
Civil Air Patrol Louisiana Wing Cessna 182-Q · Accident: undershoot during landing
From Baton Rouge Metropolitan Airport (BTR) to False River Regional Airport (HZR)
Event
- NTSB case
- FTW02LA246
- 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
- Government
- 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 182-Q
- Aircraft type
- Cessna 182
- 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
- N96725
- Operator
- Civil Air Patrol Louisiana Wing
- Onboard fatalities
- Unknown
- Route
- From Baton Rouge Metropolitan Airport (BTR), Baton Rouge, LATo False River Regional Airport (HZR), New Roads, LA
- 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
- Public Aircraft
- 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
- Undershoot
- 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
- Stall
- 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 › Proper touchdown point, not attained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The single-engine airplane landed hard on Runway 36. The 987-hour pilot reported that after completing two touch and go landings, the third landing would be a short field landing followed by a full stop. The pilot stated they were in a stable approach for Runway 36. As the airplane cleared the runway approach lights, the pilot verified the flaps were full down, and the airspeed was 60 knots. The airplane was inside the last light of the approach light system (ALS), between 50 and 100 feet AGL, when she heard the stall warning horn, and the airplane began to rapidly lose altitude. The pilot applied power; however, the airplane continued to lose altitude. The airplane touched down "hard" 40 feet short of the runway, and continued to roll for approximately 1,000 feet before coming to a stop. During the rollout, the pilot reported that the nose dropped abnormally low. The pilot instructed the passengers to unbuckle their seat belts and exit the aircraft as soon as it stopped.
Probable cause
The pilot's failure to maintain airspeed which resulted in a stall.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW02LA246
- Event ID
- 20020906X01540
- Case number
- FTW02LA246
- 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, coordinates. 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: 058cc817311dbbb32beb8567b411aee3ab99a9e8ec935004b70f81f6ad2457d4; retrieved 2026-09-18T21:18:26.283Z.