FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX03LA139 · Aero Commander 200D

21 Apr 2003 · Corona de Tucson, AZ, United States

Aero Commander 200D · Accident: in flight collision with object while maneuvering

From Marana Regional Airport (AVQ) to an unrecorded destination

Report a problem

Event

NTSB case
LAX03LA139
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
1 · 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

Aero Commander 200D

Aircraft type
Aero Commander 200
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
N243M
Operator
Unknown
Onboard fatalities
Unknown
Route
From Marana Regional Airport (AVQ), Marana, 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
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 object
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 › Clearance, not maintained
  • Pilot in command › Impairment(alcohol)
  • Pilot in command › Judgment, diminished

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

While making low passes over a construction site, the airplane collided with a trailer and came to rest about 150 yards from the first identified point of contact. Two separate toxicological tests were conducted on the pilot. The Pima County Forensic Science Center found a 0.15-percent blood alcohol level while a separate toxicological test performed by the FAA Civil Aeromedical Institute found a 100-mg/dL (0.10-percent) blood alcohol level.

Probable cause

The pilot's failure to maintain an adequate clearance from obstructions while performing low level passes. The pilot's physical impairment due to a high blood alcohol level was also causal.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX03LA139
Event ID
20030426X00575
Case number
LAX03LA139
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: 99ae28afe4e4f1c177328e6947fbb1f728992497d22a32875ddf43ea52dc6b16; retrieved 2026-09-20T19:17:39.463Z.