FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DEN07LA090 · Beech 200

24 Mar 2007 · Angel Fire, NM, United States

Beech 200 · Incident: on ground/water collision with object during landing

From Wiley Post Airport (PWA) to Angel Fire Airport (AXX)

Report a problem

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

Event

NTSB case
DEN07LA090
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
Incident
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
Instrument Meteorological Cond

Beech 200

Aircraft type
Beechcraft 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
N771HC
Operator
Unknown
Onboard fatalities
Unknown
Route
From Wiley Post Airport (PWA), Oklahoma City, OKTo Angel Fire Airport (AXX), Angel Fire, NM
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
Landing · landing roll
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
Minor Narrative disagrees

Cause areas

  • Pilot in command › Clearance, not possible

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

NTSB narrative

According to the pilot, he was performing an instrument approach on runway 17. He reported his position on the common traffic advisory frequency at 20 miles north, 10 miles north, and on a three mile final. About two miles from the approach end of the runway the pilot saw a snow plow on the northern end of the runway moving further north. The pilot maneuvered the airplane laterally to avoid over flying the snow plow and selected a touch down point 1,000 feet beyond the snow plow. Pictures of the accident airplane and runway environment, taken immediately after the accident, illustrate a swath of unplowed snow in the middle of the runway. During the landing roll, the left wing contacted the swath of snow, resulting in substantial damage. The driver of the snow plow was carrying a Unicom radio and did not hear the position reports from the pilot. No NOTAMS were issued for snow removal activity or runway conditions. An examination of the airplane's systems revealed no anomalies.

Probable cause

The pilot's inability to maintain clearance from the snow bank. Contributing factors were the pilot's failure to perform a go-around/missed approach procedure after observing snow removal equipment on the runway, the pilot's improper in-flight planning and decision making, the lack of NOTAMs for runway conditions, and the contaminated runway environment.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DEN07LA090
Event ID
20070502X00497
Case number
DEN07LA090
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: 8a99416d1d58e728602f4812b5b2beca10c01064a1d413dd18fbb1a40486c8b7; retrieved 2026-09-22T03:57:36.059Z.