WPR18LA014 · American Aviation AA 1A
American Aviation AA 1A · Accident: controlled flight into terrain/object (CFIT) on approach
From Millar Airport (2AZ4) to Millar Airport (2AZ4)
Event
- NTSB case
- WPR18LA014
- 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
American Aviation AA 1A
- Aircraft type
- American AA-1
- 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
- N9239L
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Millar Airport (2AZ4), Maricopa, AZTo Millar Airport (2AZ4), Maricopa, AZ
- 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
- 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
- Controlled flight into terrain/object (CFIT)
- 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
- 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
- Environmental issues › Physical environment
- Personnel issues › Psychological
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot was conducting a local personal flight. His son reported that his father was returning to the departure airport when the accident occurred. One witness reported that the airplane “seemed slow and too low” during the approach to land and that it struck power lines near the approach end of the runway. Subsequently, the airplane descended rapidly and impacted the runway. Several other witnesses reported that the airplane impacted unmarked power lines that were above a power line marked with orange guide balls. The pilot did not recall the accident sequence.
Postaccident examination of the airplane did not reveal any preaccident mechanical malfunctions or failures that would have precluded normal operation. Given the witness statements, it is likely that, during the approach to land, the pilot allowed the airplane to drop below the glideslope, and he failed to see and avoid the unmarked power lines that were above the marked power line.
Probable cause
The pilot’s failure to see and avoid unmarked power lines during the approach to land.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR18LA014
- Event ID
- 20171022X04025
- Case number
- WPR18LA014
- 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, 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: 3747eef3b5d17b481fe365022a3744c41de967ae38a12f67bcfa9a767ae2e975; retrieved 2026-09-16T05:57:04.166Z.