LAX05LA086 · Austin Pitts Special
Austin Pitts Special · Accident: in flight collision with terrain/water while maneuvering
From Coolidge Municipal Airport (P08) to Falcon Field (FFZ)
Event
- NTSB case
- LAX05LA086
- 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
Austin Pitts Special
- Aircraft type
- Austin PITTS SPECIAL
- 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
- N109WM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Coolidge Municipal Airport (P08), Coolidge, AZTo Falcon Field (FFZ), Mesa, 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
- Maneuvering
- 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 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 › Altitude/clearance, not maintained
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 terrain while the pilot was performing a low pass maneuver over the airport. After departure and upon reaching 100 feet above ground level (agl), the pilot configured the airplane in a 180-degree turn, in an effort to align the flight path parallel to the runway and perform a low pass over the airport. As the pilot maneuvered the airplane in close proximity to the airport surface, he experienced a loss of altitude, resulting in the underside of the right wing and right main landing gear simultaneously impacting the ramp's asphalt. The airplane collided with terrain and skidded several hundred feet. The pilot reported no preimpact mechanical malfunctions or failures with the airplane.
Probable cause
the pilot's failure to maintain an adequate altitude from the airport surface when performing an intentional low altitude flyby maneuver.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX05LA086
- Event ID
- 20050312X00304
- Case number
- LAX05LA086
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2005-02-06.
- API snapshot SHA-256: e3e8d78685bf5b87f3a3dbe85d0457110c14d7af65d6bc544d55bb600e231200; retrieved 2026-09-21T19:04:36.122Z.