FTW83LA363 · Beech B50
Beech B50 · Accident: airframe, component or system failure on approach
From Waco Regional Airport (ACT) to an unrecorded destination
Event
- NTSB case
- FTW83LA363
- 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
Beech B50
- Aircraft type
- Beechcraft 50
- 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
- N271D
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Waco Regional Airport (ACT), Waco, TXTo not recorded
- 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
- 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
- Airframe, component or system failure
- 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
- Landing gear, nose gear assembly › Failure, partial
- Propeller system/accessories, propeller slip ring › Undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PLT WAS UNABLE TO EXTEND THE NOSE GEAR PRIOR TO LANDING, SO HE ELECTED TO LAND WITH THE GEAR RETRACTED. WHILE ON FINAL APPROACH, HE CLOSED THE MIXTURES & THROTTLES AND ATTEMPTED TO FEATHER THE PROPS, BUT THE LEFT ENG CONTINUED TO WINDMILL. HE CONTINUED THE APPROACH WITH NO FLAPS, AND REPORTEDLY ARRIVED AT THE RWY WITH AN AIRSPEED OF ABOUT 140 MPH (50 MPH TOO FAST). THE 1ST TOUCHDOWN WAS MADE AT MIDFIELD. HOWEVER, THE PLT SAW THAT HE WOULD BE UNABLE TO STOP ON THE RWY. HE HAD SUFFICIENT AIRSPEED TO LIFT OUT, CLEAR A ROAD & FENCE, THEN TOUCHDOWN IN A CLEAR ZONE FOR RWY 32. AT SOME POINT DURING THE SEQUENCE, THE NOSE GEAR CAME DOWN, THE FUSELAGE WAS WRINKLED & THE PLT'S WINDSHIELD POPPED OUT. AN INVESTIGATION REVEALED THAT THE NOSE GEAR HOUSING, 50-820146, HAD FAILED, WHICH RESULTED IN THE NOSE GEAR MALFUNCTION.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record FTW83LA363
- Event ID
- 20001214X44148
- Case number
- FTW83LA363
- 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: 5f6344a5dc7deadfe630430e1999d3b8fa7ec56c9410070063a78fcb459cbf0a; retrieved 2026-09-23T21:37:08.444Z.