WPR24LA100 · Piper PA46-500TP
Pepper Equipment Piper PA46-500TP · Accident: loss of control on ground during landing
From Belen Regional Airport (BRG) to an unrecorded destination
Event
- NTSB case
- WPR24LA100
- 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
- Event fatalities
- Unknown
- 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 PA46-500TP
- Aircraft type
- Piper PA46
- 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
- N26DR
- Operator
- Pepper Equipment
- Onboard fatalities
- Unknown
- Route
- From Belen Regional Airport (BRG), Belen, NMTo not recorded
- Aircraft age
- About 16 years (built 2008)
- 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 · landing roll
- Defining eventThe 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
- Loss of control on ground
- 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
- Aircraft › Aircraft oper/perf/capability
- Aircraft › Aircraft systems
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot stated he was on a training flight when, during the third landing, he felt the airplane pull to the right and start vibrating upon touchdown. He attempted to correct to the left, but the airplane continued to the right, exited the runway, and then turned back to the left before stopping. The right aileron was substantially damaged during the event. The right tire was found deflated. Examination of the deflated tire found it was worn with little remaining tread. The exact location of a leak could not be determined due to damage to the tire. The tire was installed about 20 months and 375 flight hours prior to the accident. The number of landings on the tire was not determined. The pilot stated he thought there was sufficient tread remaining on the tire prior to the flight and he intended to replace the tire during the next annual inspection. It is likely the worn tire deflated prior to the accident landing due to excessive wear.
Probable cause
The pilot’s loss of control during landing due to a flat tire. Contributing to the accident was the pilot’s failure to replace the worn tire in a timely manner.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR24LA100
- Event ID
- 20240304193878
- Case number
- WPR24LA100
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, cause areas. 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: 545b06ae9e78e3be806fab843a89e3f595f2662fd1049cb50cefc5fca2cc6178; retrieved 2026-09-16T18:33:42.476Z.