LAX86LA229 · Piper PA-28-140
Ashton Air Service Piper PA-28-140 · Accident: loss of control on ground/water on approach
From Springerville, AZ to an unrecorded destination
Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- LAX86LA229
- 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-28-140 Possible conflict
- Aircraft type
- Piper PA-28
- 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
- N3505K
- Operator
- Ashton Air Service
- Onboard fatalities
- Unknown
- Route
- From Springerville, AZTo not recorded
- 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
- Approach · VFR go-around
- 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
- Loss of control on ground/water
- 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
- Stall/mush
- 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 › Go-around, improper
- Pilot in command › Lack of total experience
- Pilot in command › Raising of flaps, premature
- Pilot in command › Stall/mush, performed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACFT COLLIDED WITH TWO PARKED ACFT AFTER THE STUDENT PILOT LOST CONTROL DURING A GO-AROUND. THE STUDENT STATED THAT DURING HIS FIRST LANDING OF THE DAY THE ACFT STARTED TO 'SLIDE SIDEWAYS' AND HE ELECTED TO GO-AROUND. HE INCREASED THE THROTTLE AND THE ACFT DRIFTED OFF THE RUNWAY AND EVENTUALLY BECAME AIRBORNE. HE THEN REALIZED THAT HE STILL HAD THE FLAPS IN THE FULL DOWN POSITION. REMEMBERING THAT HIS FLIGHT INSTRUCTOR TOLD HIM IT WAS WRONG TO TAKE OFF WITH FULL FLAPS, THE STUDENT PILOT RETRACTED THE FLAPS TO THE FULL UP POSITION. THE ACFT SETTLED ONTO THE RAMP AREA AND THE STUDENT ATTEMPTED TO TAKE OFF AGAIN BY APPLYING FULL POWER. THE ACFT ACCELERATED AND STRUCK TWO PARKEDACFT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX86LA229
- Event ID
- 20001213X33605
- Case number
- LAX86LA229
- 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: c14ced2dd1d5de790956e12a621d1cf8641d2f6dc4274b7b4b1387e56ba5ec96; retrieved 2026-09-23T14:40:09.963Z.