FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR12CA073 · McAdam W E CHRISTEN EAGLE II

1 Jan 2012 · Eureka, CA, United States

McAdam W E CHRISTEN EAGLE II · Accident: airport occurrence during landing

From Murray Field (EKA) to Murray Field (EKA)

Report a problem

Event

NTSB case
WPR12CA073
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

McAdam W E CHRISTEN EAGLE II

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
N45WM
Operator
Unknown
Onboard fatalities
Unknown
Route
From Murray Field (EKA), Eureka, CATo Murray Field (EKA), Eureka, CA
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
Defining eventThe 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
Airport occurrence
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

  • Environmental issues › Physical environment

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

NTSB narrative

The pilot reported that, during the landing flare, he noticed a deer (or possibly several deer) move onto the runway. In response, he added power and attempted to maneuver away from the animal(s). The airplane impacted what he believed to be a deer. The pilot realized that the airplane had likely incurred damage that could hinder further flight, so he retarded the engine power and landed without further incident. The left wing sustained substantial damage to the leading edge. The pilot reported no mechanical malfunctions or failures with the airplane that would have precluded normal operation. The Federal Aviation Administration Airport Facilities Directory for the airport contained a note stating that there are deer occasionally on the runway.

Probable cause

A collision with a deer while landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR12CA073
Event ID
20111230X02532
Case number
WPR12CA073
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2012-01-02.
  • API snapshot SHA-256: 28809e6c74250220be80413b63338c0370e858466feb74174dd3a2acf064842c; retrieved 2026-09-15T17:01:56.522Z.