DFW06CA018 · Piper PA28A
Piper PA28A · Accident: airframe, component or system failure during landing
From Lubbock, TX to Lubbock, TX
Event
- NTSB case
- DFW06CA018
- 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 PA28A
- Aircraft type
- Piper PA28
- 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
- N828MC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Lubbock, TXTo Lubbock, 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
- 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, axle › Not secured
- Landing gear, wheel › Separation
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The 485-hour flight instructor and the 11-hour student pilot were executing a crosswind landing during a local training flight. Shortly after touch down on Runway 17R, the nose landing gear collapsed, and the airplane began to skid down the runway. While attempting to bring the airplane to a stop, the propeller and left wing contacted the ground. The winds at the time of the mishap were reported from 180 degrees at 11 knots. An examination of the airplane by an Federal Aviation Administration (FAA) inspector revealed that the axel for the nose landing gear was missing and it was later located along the centerline of the runway. The lock nut securing the axle to the landing gear assembly was not located, and it was not determined why the nut was not in place. The last annual inspection was completed on October 24, 2005, about 22.2 hours prior to the mishap. No recent maintenance was reported on the nose landing gear assembly.
Probable cause
The pilot's inability to maintain directional control of the airplane while landing due to the separation of the nose landing gear tire assembly.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW06CA018
- Event ID
- 20051130X01918
- Case number
- DFW06CA018
- 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: 0bc2b850ddb6f2057ed704377e4faaedd780e8ec46c83ae094ee2159de65649d; retrieved 2026-09-22T05:15:57.642Z.