# NTSB GAA19CA153: Cessna 172, N5338N, Princeton, NJ, February 23, 2019 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: February 23, 2019, 18:40 local (23:40 UTC) - Place: Princeton, NJ - Coordinates: 40.399166, -74.658889 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=40.3992&lon=-74.6589&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing: Wildlife encounter (non-bird)](https://openairdocs.org/ntsb-events/310) - Highest injury: No injuries - Injuries: 3 uninjured - Status: Completed, report September 26, 2019 - Report: Approved by Office Director - NTSB office: General Aviation Accidents - Parties: FAA - NTSB case key (mKey): 99032 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA19CA153 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/99032/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=99032 - Page: https://openairdocs.org/ntsb/GAA19CA153 ## Probable cause A collision with deer on the runway while landing at night and the airport's lack of a complete 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 · Effect on operation (probable cause); cases with it: [Cessna 172S, 16 cases](https://openairdocs.org/ntsb-findings/03022045/cases.md?model=2072439), [All aircraft, 358 cases](https://openairdocs.org/ntsb-findings/03022045/cases.md) - [Object/animal/substance: fence/fence post](https://openairdocs.org/ntsb-findings/03022047): Environmental issues › Physical environment · Use of related info (probable cause); cases with it: [Cessna 172S, 7 cases](https://openairdocs.org/ntsb-findings/03022047/cases.md?model=2072439), [All aircraft, 313 cases](https://openairdocs.org/ntsb-findings/03022047/cases.md) - [Object/animal/substance: animal(s)/bird(s)](https://openairdocs.org/ntsb-findings/03022045): Environmental issues › Physical environment · Ability to respond/compensate (probable cause); cases with it: [Cessna 172S, 16 cases](https://openairdocs.org/ntsb-findings/03022045/cases.md?model=2072439), [All aircraft, 358 cases](https://openairdocs.org/ntsb-findings/03022045/cases.md) - [Light condition: dark](https://openairdocs.org/ntsb-findings/03036020): Environmental issues › Conditions/weather/phenomena · Effect on personnel; cases with it: [Cessna 172S, 19 cases](https://openairdocs.org/ntsb-findings/03036020/cases.md?model=2072439), [All aircraft, 448 cases](https://openairdocs.org/ntsb-findings/03036020/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing: Wildlife encounter (non-bird)](https://openairdocs.org/ntsb-events/310) (defining event); cases with it: [Cessna 172S, 4 cases](https://openairdocs.org/ntsb-events/310/sequence.md?model=2072439), [All aircraft, 107 cases](https://openairdocs.org/ntsb-events/310/sequence.md) ## Analysis The pilot reported that, while landing at night, the airplane struck two deer on the runway. He added that he did not see the deer on the runway during the approach and landing. The airplane sustained substantial damage to the right horizontal stabilizer. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. The Federal Aviation Administration (FAA) Airport Facility Directory for the accident airport, stated, in part, "Deer and birds on and [in the vicinity of the airport]." The pilot stated that the airport's fencing was intermittent and that deer were frequently seen around the airport. The airport manager added that the airport's perimeter fence only covered the eastern and southern perimeter and that a deer strike occurred at least once every 2 years. However, according to the FAA Wildlife Strike Database the last reported wildlife strike at the accident airport occurred on April 10, 2012. The FAA's Part 139 CertAlert, No. 16-03, "Recommended Wildlife Exclusion Fencing," which provides airfield exclusion methods for deer and other large mammals, recommends constructing fencing "fully around the airfield without gaps." ## Factual narrative The pilot reported that, while landing at night, the airplane struck two deer on the runway. He added that he did not see the deer on the runway during the approach and landing. The airplane substantial damage to the right horizontal stabilizer. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. The Federal Aviation Administration (FAA) Airport Facility Directory, for the accident airport, in part stated: "Deer and birds on and [in the vicinity of the airport]." The pilot stated that the airport's fencing was intermittent, and that deer were frequently seen in and around the airport. Airport Manager added that the airport's perimeter fence only covered the eastern and southern perimeter and that a deer strike occurred at least once every two years. According to the Federal Aviation Administration (FAA) Wildlife Strike Database, for the accident airport, the last reported wildlife strike occurred on April 10, 2012. The FAA maintains a comprehensive program to address wildlife hazard through a database and a reporting strike form. (For more information, see Form Approved OMB No. 2120-0045 in the public docket.) The FAA, under National Part 139 CertALert, No. 16-03, Recommended Wildlife Exclusion Fencing, provides airfield exclusion methods for deer and other large mammals. (For more information, see CertALert No. 16-03 in the public docket.) ## Aircraft - Registration: [N5338N](https://openairdocs.org/aircraft/N5338N), registered now, S/N 172S9358, built 2003 (OpenAirDocs) - Reported make and model: Cessna 172 (S) - Registry model: [Cessna 172S](https://openairdocs.org/model/cessna-172s) (registry code 2072439) (OpenAirDocs) - Registry engine: [Lycoming IO-360-L2A](https://openairdocs.org/engine/lycoming-io-360-l2a) (registry code 41597, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 172S9358 - Year built: 2003 - Airframe hours: 8772 - Engines: Lycoming IO-360-L2A 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Raritan Valley Flying School - Registered owner: Raritan Valley Flying School - Airworthiness certificate: Standard, Utility; Standard, Normal - Last inspection: 100 hour, January 23, 2019 - Departed: 39N, Princeton, NJ - Destination: 39N, Princeton, NJ - Airport: 39N, Princeton, runway 10, 3,499 × 75 ft, asphalt - Equipment: Handheld GPS, Electronic flight bag or handheld device ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 30; injuries: none; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; last flight review August 23, 2017; seat: left; restraint: 3-point; flight hours: 296.1 total, 129.1 in this make and model, 249.6 as pilot in command, 18.5 in the last 90 days, 2.2 in the last 30 days ## Weather - Conditions: Visual (VMC), Night - Wind: 90° at 6 knots - Visibility: 10 statute miles - Lowest ceiling: 5,500 ft overcast - Temperature: 39 °F, dew point 30 °F - Altimeter: 30.29 inHg - Observed at: KTTN, 10 nm away ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20190223014949A](https://openairdocs.org/incident/20190223014949A), Feb 23, 2019: Cessna 172S, Princeton, NJ, Substantial damage. Personal flight operated under part 91 during VFR night conditions terminated with normal landing at departure airport. During rollout aircraft struck deer… ## Docket (6 files) The files NTSB released with the investigation on June 25, 2019, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=99032. 1.2 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 627 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40473651&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Accident Photo (item 2, .PDF, 1 photo, 157 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40473652&FileExtension=.PDF&FileName=Accident%20Photo-Master.PDF - Pilot Record of Conversation (item 3, .PDF, 62 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40473653&FileExtension=.PDF&FileName=Pilot%20Record%20of%20Conversation-Master.PDF - Airport Manager Record of Conversation (item 4, .PDF, 96 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40473654&FileExtension=.PDF&FileName=Airport%20Manager%20Record%20of%20Conversation-Master.PDF - Airport Facilities Directory - Accident Airport (item 5, .PDF, 62 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40473655&FileExtension=.PDF&FileName=Airport%20Facilities%20Directory%20-%20Accident%20Airport-Master.PDF - CertAlert No. 16-03 - Recommended Wildlife Exclusion Fencing (item 6, .PDF, 198 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40473656&FileExtension=.PDF&FileName=CertAlert%20No.%2016-03%20-%20Recommended%20Wildlife%20Exclusion%20Fencing-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.