# NTSB WPR12CA375: Cessna 172, N3082E, Sand Point, ID, August 28, 2012 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: August 27, 2012, 19:45 local (Aug 28, 2012, 02:45 UTC) - Place: Sand Point, ID - Coordinates: 48.276668, -116.552223 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=48.2767&lon=-116.5522&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Wildlife encounter (non-bird)](https://openairdocs.org/ntsb-events/310) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report December 5, 2012 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 84846 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR12CA375 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/84846/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=84846 - Page: https://openairdocs.org/ntsb/WPR12CA375 ## Probable cause A deer strike during the landing flare. Contributing to the accident was the airport’s lack of any deer incursion prevention measures, such as an airport perimeter fence. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Object/animal/substance: animal(s)/bird(s)](https://openairdocs.org/ntsb-findings/03022045): Environmental issues › Physical environment · Contributed to outcome (probable cause); cases with it: [Cessna 172N, 7 cases](https://openairdocs.org/ntsb-findings/03022045/cases.md?model=2072434), [All aircraft, 358 cases](https://openairdocs.org/ntsb-findings/03022045/cases.md) - [Airport facilities/design: security](https://openairdocs.org/ntsb-findings/03017080): Environmental issues › Operating environment · Contributed to outcome (probable cause); cases with it: [Cessna 172N, 1 case](https://openairdocs.org/ntsb-findings/03017080/cases.md?model=2072434), [All aircraft, 4 cases](https://openairdocs.org/ntsb-findings/03017080/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-flare/touchdown: Wildlife encounter (non-bird)](https://openairdocs.org/ntsb-events/310) (defining event); cases with it: [Cessna 172N, 2 cases](https://openairdocs.org/ntsb-events/310/sequence.md?model=2072434), [All aircraft, 107 cases](https://openairdocs.org/ntsb-events/310/sequence.md) - [Landing-flare/touchdown: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna 172N, 134 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2072434), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The flight instructor and the student pilot had conducted a night visual flight rules instructional flight and were returning to their home base, a nontower-controlled airport. The student pilot set the airplane up for landing, and, according to the flight instructor, they looked carefully but did not see any wildlife on or near the runway throughout the approach and flare. However, during the flare, a deer ran onto the left side of the runway and collided with the airplane’s left horizontal stabilizer. The pilots maintained control of the airplane, and the subsequent touchdown and landing roll were uneventful. The airplane’s stabilizer was substantially damaged. According to the flight instructor, this was the third deer strike at that airport in as many years. The Federal Aviation Administration (FAA) Airport/Facility Directory stated that wildlife was present on and in the vicinity of the airport, and the flight instructor reported that a similar message was normally contained in the airport's automated weather observing system radio broadcast. Postaccident discussions with the airport manager and FAA personnel revealed that deer are a known problem at the airport, and that efforts are underway to approve, fund, and install an airport perimeter fence no sooner than fall 2014. Discussions with United States Department of Agriculture Wildlife Management Division personnel revealed that the agency’s local office was willing and able to provide direct technical assistance to the airport to explore and implement deer hazard mitigation strategies in the interim. ## Factual narrative The certified flight instructor (CFI) and the student pilot had conducted a night visual flight rules instructional flight and were returning to their home, non-towered airport. The student pilot set up for landing on runway 1, and according to the CFI, they looked carefully for wildlife on and near the runway throughout the approach and flare, and did not observe any. During the flare, a deer ran onto the runway from the grass adjacent to the left runway edge, and struck or was struck by the left horizontal stabilizer. The pilots maintained control of the airplane, and the touchdown and rollout were uneventful. The stabilizer was substantially damaged, and the pilots were uninjured. According to the CFI, this was the third deer strike at that airport in as many years. The Federal Aviation Administration (FAA) Airport/Facility Directory stated that wildlife was present on and in the vicinity of the airport, and the CFI reported that a similar message was normally contained in the airport's AWOS (automated weather observing system) radio broadcast. NTSB discussions with the airport manager and personnel from the FAA revealed that deer are a known problem at the airport, and that efforts are underway to approve, fund, and install an airport perimeter fence no sooner than approximately fall 2014. Discussions with United States Department of Agriculture (USDA) Wildlife Management Division personnel revealed that the local office of the USDA was willing and able to provide direct technical assistance to the airport to explore and implement deer hazard mitigation strategies in the interim. ## Aircraft - Registration: [N3082E](https://openairdocs.org/aircraft/N3082E), registered now, S/N 17271435, built 1978 (OpenAirDocs) - Reported make and model: CESSNA 172 (N) - Registry model: [Cessna 172N](https://openairdocs.org/model/cessna-172n) (registry code 2072434) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17271435 - Airframe hours: 3880 - Engines: LYCOMING O-320 160 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Operator: Silverwing Flight Services - Registered owner: Silverwing Flight Services - Airworthiness certificate: Standard, Normal - Last inspection: 100 hour, August 22, 2012 - Departed: SZT, Sand Point, ID - Destination: SZT, Sand Point, ID - Flight plan: Unknown - Airport: SZT, Sandpoint, runway 01, 5,500 × 75 ft, macadam ## Flight crew As NTSB recorded them. NTSB leaves out names. - Flight instructor; age 63; injuries: none; commercial, flight instructor; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 2, with waivers/limitations; seat: right; flight hours: 5,000 total, 1,000 in this make and model, 21 in the last 90 days, 15 in the last 30 days, 2 in the last 24 hours - Student pilot; age 18; injuries: none; student; medical: class 1, with waivers/limitations; seat: left; flight hours: 55 total, 55 in this make and model, 25 in the last 90 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Night - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 64 °F - Observed at: SZT ## Docket (7 files) The files NTSB released with the investigation on October 12, 2012, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=84846. 3.1 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 1.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40378659&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Flight Instructor's Statement (item 2, .PDF, 74 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40378666&FileExtension=.PDF&FileName=Flight%20Instructor%27s%20Statement-Redacted.PDF - Record of Conversation - FAA Inspector (item 3, .PDF, 36 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40378661&FileExtension=.PDF&FileName=Record%20of%20Conversation%20-%20FAA%20Inspector-Master.PDF - Record of Conversation - Airport Manager (item 4, .PDF, 37 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40378667&FileExtension=.PDF&FileName=Record%20of%20Conversation%20-%20Airport%20Manager-Master.PDF - Record of Conversation - USDA Wildlife Agent (item 5, .PDF, 37 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40378668&FileExtension=.PDF&FileName=Record%20of%20Conversation%20-%20USDA%20Wildlife%20Agent-Master.PDF - Photo 1. Damage to Left Tailplane (item 6, .PDF, 901 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40378664&FileExtension=.PDF&FileName=Photo%201.%20Damage%20to%20Left%20Tailplane-Master.PDF - Photo 2. Damage to Right Aft Fuselage (item 7, .PDF, 880 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40378665&FileExtension=.PDF&FileName=Photo%202.%20Damage%20to%20Right%20Aft%20Fuselage-Master.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.