CEN21LA312 · Piper PA 46-350P
Piper PA 46-350P · Accident: loss of control on ground during landing
From Tri-Cities Regional TN/VA Airport (TRI) to an unrecorded destination
Event
- NTSB case
- CEN21LA312
- 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 PA 46-350P
- Aircraft type
- Piper PA-46
- 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
- N110ST
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Tri-Cities Regional TN/VA Airport (TRI), Blountville, TNTo not recorded
- Aircraft age
- About 16 years (built 2005)
- 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
- Environmental issues › Physical environment
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that while landing on a wet runway and as he applied brakes during the landing roll, the airplane began to hydroplane, and the nose landing gear collapsed. The airplane veered left and exited the side of the runway coming to a stop in the grass. The airplane sustained substantial damage to the engine mount. The pilot reported there were no preimpact mechanical failures or malfunctions with the airframe and engine that would have precluded normal operation. A review of the airplane’s maintenance records revealed that Piper Aircraft Service Bulletin (SB) 1103F (a recurring inspection of the engine mount for cracks every 100 hours) was complied with only once in the airplane’s service history, which was about 437 hours before the accident occurred. Based on the available information, it was undetermined if any preexisting defects in the engine mount contributed to nose landing gear collapse. The pilot reported the accident could have been prevented by “not applying brakes” and allowing a “continued roll out.”
Probable cause
The pilot’s failure to maintain directional control during the landing roll with hydroplaning conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN21LA312
- Event ID
- 20210709103447
- Case number
- CEN21LA312
- 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, 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: a395f15b6b72ac0ee6b32918117e0956af2028f3630a85b114bc24d2cdbc6110; retrieved 2026-09-16T14:16:26.793Z.