FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX04LA313 · Redgate Europa Classic

2 Sept 2004 · Marble Canyon, AZ, United States

Redgate Europa Classic · Accident: in flight collision with terrain/water

From LGB · Marble Canyon, AZ to Bullfrog Basin Airport (U07)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
LAX04LA313
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
2 · 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

Redgate Europa Classic

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
N912EE
Operator
Unknown
Onboard fatalities
Unknown
Route Possible conflict
From LGB · Marble Canyon, AZTo Bullfrog Basin Airport (U07), GLEN CANYON NAT, UT
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
Unknown
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
Destroyed

Cause areas

  • Reason for occurrence undetermined

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

NTSB narrative

The aircraft collided with desert terrain under unknown circumstances and the wreckage was spotted by a passing aircraft 2 days after the probable accident date. On the day of the accident, good visual meteorological conditions existed. Examination of ground scars and damage patterns in the wreckage suggests that the airplane collided with the level desert terrain in a nose low and approximately a wings level attitude. Although the wreckage location is consistent with the airplane being on a right base leg for runway 3 or an attempted 180-degree return to runway 21 maneuver; the investigation was unable to determine if the event occurred during initial climb or during landing approach to an airport located about 1 mile away. Earlier during the day, the pilot had landed at the airport. An entry was noted on the airport's sign-in sheet indicating that the pilot had been there for lunch. No witnesses recalled observing the pilot depart from the uncontrolled airport, and his takeoff time was estimated as being after noon. An examination of the airplane wreckage revealed two of the three propeller blades were fractured; the third blade appeared intact. Blade fragments were found in the ground at the initial point of impact (IPI). The distance from the IPI to the farthest piece of wreckage was about 65 feet, and the track was nearly perpendicular to the runway. No evidence of preimpact mechanical malfunction was observed with the airframe or engine. Although evidence was found consistent with the crankshaft rotating during the impact sequence, no determination was made regarding whether the engine was developing power.

Probable cause

an in-flight collision with terrain for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX04LA313
Event ID
20040910X01393
Case number
LAX04LA313
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: 86acd29b931607328b6809671dba3acd26d6439d1e4994c6c055aac10241f4b7; retrieved 2026-09-20T18:21:16.772Z.