LAX03LA154 · Piper PA-32R-301T
Piper PA-32R-301T · Accident: in flight collision with object during initial climb
From Big Springs Ranch Airport (AZ27) to Salt Lake City International Airport (SLC)
Event
- NTSB case
- LAX03LA154
- 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 PA-32R-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
- N99TX
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Big Springs Ranch Airport (AZ27), Paulden, AZTo Salt Lake City International Airport (SLC), Salt Lake City, 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
- Initial climb
- 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
- In flight collision with object
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Wire, transmission
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Airspeed, not obtained/maintained
- Pilot in command › Climb, not attained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane collided with power lines in the takeoff initial climb from a dirt airstrip. The pilot said that in the takeoff roll he noticed that it was taking longer than normal to lift off from the dirt airport. Upon rotation the pilot maintained a nose high attitude attempting to climb, but the pilot did not retract the landing gear. The airplane remained in ground effect and would not climb. The airplane struck a set of utility lines at the end of the runway. The density altitude was computed to be 6,167 feet. The pilot said that there were no mechanical malfunctions with either the engine or the airframe.
Probable cause
the pilot's failure to attain and maintain the proper climb airspeed. The high density altitude condition was a factor.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX03LA154
- Event ID
- 20030520X00699
- Case number
- LAX03LA154
- 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: 6bb2501e05bdac9de587f5b11d78bbb2ad102f5dfb337fce2784504fe57cfcca; retrieved 2026-09-21T19:29:12.916Z.