Pro Aire Cargo & Consulting Piper PA-31T3 accident
Piper PA-31T3 · Accident: loss of control on ground while taxiing
From Appleton International Airport (ATW) to Menominee–Marinette Twin County Airport (MNM)
Event
- NTSB case
- CEN25LA293
- 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
- 0
- 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
- Charter & commuter
- 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-31T3
- Aircraft type
- Piper PA-31
- 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
- N401VA
- Operator
- Pro Aire Cargo & Consulting
- Onboard fatalities
- Unknown
- Route
- From Appleton International Airport (ATW), Appleton, WITo Menominee–Marinette Twin County Airport (MNM), Menominee, MI
- Aircraft age
- About 43 years (built 1982)
- 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 135: Air Taxi & Commuter
- 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
- Taxi
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that during engine start up, he applied the brakes to the cargo airplane and remained stationary while he received a taxi clearance. As he released the brakes to begin taxiing, the brake pedals went to the floor with no braking action. He pumped the brakes several times with no effect, so he feathered both propellers and shut down the engines. The airplane continued to roll and collided with a parked airplane on the ramp. Postaccident examination revealed that the airplane sustained substantial damage to the left wing. A functional check revealed that the brake system was operational with no malfunctions noted. The left main landing gear brake pads were worn beyond allowable limits. The examination did not reveal any other anomalies that would have precluded normal operation. While the left brake pads were worn beyond allowable limits, the main landing gear braking action would have still been available to the pilot.
Probable cause
The pilot’s failure to maintain control of the airplane on the ground, which resulted in a collision with a parked airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN25LA293
- Event ID
- 20250728200650
- Case number
- CEN25LA293
- 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: 9f6e302d2e2bd2e0eabc590c538282d42fa3a2b985022c376c7eeaf3abd579c4; retrieved 2026-09-16T20:08:44.518Z.