SEA82DA036 · Piper PA-32-301T
Piper PA-32-301T · Accident: on ground/water collision with terrain/water during takeoff
From Friedman Memorial Airport (SUN) to Provo, UT
Event
- NTSB case
- SEA82DA036
- 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
- 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-32-301T
- Aircraft type
- Piper PA-32
- 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
- N83764
- Operator
- Larry V. Lowe · private individual
- Onboard fatalities
- Unknown
- Route
- From Friedman Memorial Airport (SUN), Hailey, IDTo Provo, UT
- 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
- Takeoff
- 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
- On ground/water collision with terrain/water
- 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 › Parking brakes, improper use of
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
AFTER AN ENGINE RUN-UP WITH THE PARKING BRAKE SET, THE FIRST ATTEMPT TO TAKEOFF WAS ABORTED WHEN THE PLANE FAILED TO ACCELERATE SATISFACTORILY. THE BRAKES OPERATED SATISFACTORILY DURING THE ABORT AND A SECOND RUN-UP REVEALED NO UNUSUAL ENGINE INDICATIONS. WHILE TAXIING BACK TO THE APPROACH END OF THE RUNWAY, THE PILOT NOTED A LACK OF RIGHT BRAKING ACTION. HE ASKED THE PASSENGER IN THE RIGHT FRONT SEAT TO CHECK THE RIGHT SET OF BRAKES, THEN HE DETERMINED THE BRAKES WERE ACCEPTABLE. DURING A SECOND ATTEMPT T0 TAKEOFF, THE PILOT FELT THERE WAS UNSATISFACTORY ACCELERATION AND ABORTED AGAIN. HOWEVER, HE REPORTED NO BRAKING ACTION WAS AVAILABLE. HE USED AERODYNAMIC BRAKING AND FISHTAILED TO SLOW THE AIRCRAFT, AND FINALLY, HE RAN INTO A SNOWBANK AT THE DEPARTURE END OF THE RUNWAY. AN EXAMINATION OF THE BRAKES ONLY REVEALED EVIDENCE OF EXCESSIVE HEAT. LOCAL MAINTENANCE PERSONNEL REPORTED THAT THE PARKING BRAKE RELEASE TRIGGER MUST BE HELD IN THE DEPRESSED POSTION WHILE MOVING THE BRAKE HANDLE FORWARD TO PREVENT INADVERTENT BRAKING.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record SEA82DA036
- Event ID
- 20020917X02591
- Case number
- SEA82DA036
- 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. 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: 1458b58e8dfcb40630be02efcb7cbf14bc994ac7c618d83ada19993968d42b4b; retrieved 2026-09-24T03:33:22.144Z.