DFW07LA021 · Piper PA32-301XTC
Piper PA32-301XTC · Accident: hard landing
From Lubbock Preston Smith International Airport (LBB) to San Marcos Regional Airport (HYI)
Event
- NTSB case
- DFW07LA021
- 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
Piper PA32-301XTC
- Aircraft type
- Piper PA32
- 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
- N506C
- Operator
- Donald L Curry · private individual
- Onboard fatalities
- Unknown
- Route
- From Lubbock Preston Smith International Airport (LBB), Lubbock, TXTo San Marcos Regional Airport (HYI), San Marcos, 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
- 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 › Recovery from bounced landing, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
While landing on Runway 26, a 6,330-foot long, by 100-foot wide asphalt runway, the single-engine airplane bounced and started to porpoise. Each successive bounce got higher in altitude until ultimately the airplane's nose landing gear collapsed and the propeller impacted the ground. The airplane came to rest in the upright position and the 735-hour private pilot and his passenger were able to exit the airplane unassisted. There was no fire. During the post-accident investigation, the rudder pedals were functionally checked and continuity was established from the rudder pedals to the steering rods and rudder. No pre- impact anomalies were noted with the airplane's flight controls, nose landing gear, or steering mechanism. The wind at the time of the accident was reportedly from 250 degrees at 6 knots.
Probable cause
The pilot's improper recovery from a bounced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW07LA021
- Event ID
- 20070116X00057
- Case number
- DFW07LA021
- 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: b13701e8f5cd6f778abe4d4c3b41211ab743a7dbf21d1c3049a8bcbdb400e87f; retrieved 2026-09-22T04:16:40.660Z.