Air Vegas Flight 12
Beech 99-C99 · Accident: in flight collision with object while maneuvering
From Grand Canyon National Park Airport (GCN) to L15 · Henderson, NV
Event
- NTSB case
- LAX98FA013
- 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
- 0
- 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
- Airline
- 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 99-C99
- Aircraft type
- Beechcraft 99
- 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
- N227AV
- Operator
- Air Vegas
- Onboard fatalities
- Unknown
- Route
- From Grand Canyon National Park Airport (GCN), Grand Canyon, AZTo L15 · Henderson, NV
- 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 121: Air Carrier
- 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
- 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, transmission
- 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 › In-flight planning/decision, inadequate
- Pilot in command › Visual lookout, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The captain saw a car trailing smoke along a dirt road and decided to descend from his en route altitude and investigate. After overflying the car, he continued flying over the road at low level until the first officer warned of wires. He was unable to react in time to avoid striking the wires. After the collision, the captain elected to continue to his destination. During the approach, they heard a loud thud and the left engine began shaking. The captain reduced the power and declared an emergency. After a positive visual gear check by the tower, the captain landed the aircraft. The crew shut down the left engine as they taxied to the ramp. Broken sections of wire were found embedded in the forward fuselage and vertical stabilizer. The tip of one blade was missing from the left propeller and the nose section was shattered. Neither of the ground witnesses reported any malfunction with their vehicles during this time.
Probable cause
The pilot's inadequate in-flight decision, inadequate visual lookout, and his failure to maintain adequate obstacle clearance. Contributing was low altitude flight.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX98FA013
- Event ID
- 20001208X09047
- Case number
- LAX98FA013
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- 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. 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: 7ae83df142ab9a187a6a87a55a8c5ac96236ea690de8f500c7e281e9704b9bfc; retrieved 2026-09-18T17:20:35.763Z.
- The NTSB's operator name is blank for N227AV; the operator shown is the name the NTSB records it doing business as.