The U.S. aircraft register, updated daily
Accidents · NTSB WPR12CA073 · Final report

Amateur-built CHRISTEN EAGLE II accident near Eureka, California, January 2, 2012

On January 2, 2012, a amateur-built CHRISTEN EAGLE II, registered N45WM, was substantially damaged in an accident during landing (landing roll) near Eureka, California (Murray Field Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

A collision with a deer while landing.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
January 2, 2012
Place
Eureka, California · Murray Field Airport · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Amateur-built CHRISTEN EAGLE II
Registration
N45WM · no longer on the register · serial MCADAM-0001
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Airport occurrence during landing (landing roll) defining event
  2. Collision with terrain or object (not controlled flight into terrain) during landing (landing roll)

The NTSB's findings

  • cause Environmental issues › Physical environment › Object/animal/substance › Animal(s)/bird(s) › Effect on equipment
  • cause Environmental issues › Physical environment › Object/animal/substance › Animal(s)/bird(s) › Ability to respond/compensate

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 1,131 hours in all; 348 in this make and model; 6 in the last 90 days
  • Medical certificate: Class 3 (without waivers/limitations)
  • Injury: no injuries

The aircraft

  • Maximum gross weight: 1,600 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Lycoming AEIO-360-A1D (piston); 0 hours total

The flight

  • Departed from: EKA Eureka CA
  • Destination: EKA Eureka CA
  • Flight plan: not recorded
  • Runway 12, 3,000 ft by 75 ft

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 55°F (13°C), dew point 0°F (-18°C)

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.