LAX04CA065 · Beech 58P
Beech 58P · Accident: on ground/water collision with object while taxiing
From Montgomery-Gibbs Executive Airport (MYF) to Aspen-Pitkin County Airport (Sardy Field) (ASE)
Event
- NTSB case
- LAX04CA065
- 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
Beech 58P
- Aircraft type
- Beechcraft 58
- 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
- N58JG
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Montgomery-Gibbs Executive Airport (MYF), San Diego, CATo Aspen-Pitkin County Airport (Sardy Field) (ASE), Aspen, CO
- 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
- Taxi · to runway
- 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
- On ground/water 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
- Substantial
Cause areas
- Pilot in command › Clearance, not maintained
- Pilot in command › Visual lookout, inadequate
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 a parked, unoccupied, vehicle while taxiing to the active runway. The pilot said that while taxiing, he noticed a red truck parked on the right side of the taxiway. He maneuvered the airplane so that the nose gear was about 1 foot to the left of the taxiway centerline, and attempted to avoid the vehicle. He estimated that he was taxiing about 7 miles per hour when the right wing contacted the truck's cab and he felt the airplane suddenly veer sharply to the right. The right propeller made contact with the front of the truck, and he applied the brakes. After the airplane came to a complete stop, he shut down both engines. The pilot stated that there were no preimpact mechanical malfunctions or failures with the airplane.
Probable cause
the pilot's inadequate lookout, which resulted in his failure to maintain clearance from the vehicle while taxiing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX04CA065
- Event ID
- 20040114X00064
- Case number
- LAX04CA065
- 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: 174ade65477ccf88c8ee7596300c2ccbf3c6e0f34108cbd5b7d3f361763b8a50; retrieved 2026-09-22T08:05:43.345Z.