FTW02LA069 · Bellanca 17-30
Bellanca 17-30 · Accident: undershoot on approach
From St Johns Industrial Air Park (SJN) to Hale County Airport (PVW)
Event
- NTSB case
- FTW02LA069
- 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
Bellanca 17-30
- Aircraft type
- Bellanca 17
- 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
- N7388V
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From St Johns Industrial Air Park (SJN), St. Johns, AZTo Hale County Airport (PVW), Plainview, 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
- Approach · VFR pattern final
- 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
- 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 glidepath, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, he set up the approach to land on runway 22 so that the airplane would touch down on the numbers. Following a normal traffic pattern, the pilot flared the airplane and it landed 12 feet short of the runway. Subsequently, the airplane's nose landing gear contacted the lip at the approach end of the runway and collapsed. The airplane then slid down the runway along the runway centerline and came to a stop upright.
Probable cause
the pilot's failure to maintain the proper glidepath, which resulted in landing short of the runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW02LA069
- Event ID
- 20020118X00089
- Case number
- FTW02LA069
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2002-01-16.
- API snapshot SHA-256: 7d1fd3ca11d3d7ca322138e4fff23a314fb48ebaa3ebd9ce6e098e2031489a17; retrieved 2026-09-22T11:11:47.478Z.