FTW95LA095 · Beech 33-A
Beech 33-A · Accident: hard landing
From Monroe Regional Airport (MLU) to 5R3 · TX
Event
- NTSB case
- FTW95LA095
- 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
- Instrument Meteorological Cond
Beech 33-A
- Aircraft type
- Beechcraft 33
- 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
- N55VS
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Monroe Regional Airport (MLU), Monroe, LATo 5R3 · TX
- 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
- Hard 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 › Missed approach, not performed
- Pilot in command › Proper descent rate, exceeded
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT STATED THAT AFTER EXECUTING A CIRCLING VOR/DME APPROACH, HE DID NOT HAVE VISUAL REFERENCE WITH THE AIRPORT UNITL THE AIRPLANE WAS 'ALMOST ON TOP OF THE RUNWAY' AT 600 FEET ABOVE GROUND LEVEL (AGL). HE COMMENCED A DESCENDING, 'TIGHT' RIGHT TURN TO KEEP THE RUNWAY IN SIGHT. DESCENDING BELOW 300 FEET, THE PILOT CONTINUED A 'STEEP' TURN ON A 45 DEGREE BEARING TO THE RUNWAY TO INTERCEPT FINAL. HE STATED THAT AS HE 'STARTED TO LEVEL THE WINGS TO LAND, THE AIRCRAFT JUST DROPPED.' THE PILOT FURTHER STATED THAT 'THE RIGHT WING IMPACTED THE RUNWAY AND THE AIRPLANE SKIDDED OFF THE SIDE OF THE RUNWAY.' THE PILOT REPORTED WEATHER CONDITIONS OF FOG AND DRIZZLE DURING THE APPROACH. THE PUBLISHED MISSED APPROACH POINT FOR THE APPROACH WAS 5 MILES FROM THE FINAL APPROACH FIX AND 7/10 MILE NORTHWEST OF THE RUNWAY MIDPOINT.
Probable cause
THE PILOT'S FAILURE TO EXECUTE A MISSED APPROACH AT MINIMUMS FOR THE NON-PRECISION APPROACH AND AN EXCESSIVE RATE OF DESCENT DURING THE CIRCLE TO LAND MANEUVER.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW95LA095
- Event ID
- 20001207X02864
- Case number
- FTW95LA095
- 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: 28d161d6092b4abe7437c1e491ecb3560e1703a92c09572333bca4c4762cfeea; retrieved 2026-09-23T00:18:05.826Z.