GAA16CA129 · Pilatus PC12 45
Quest Diagnostics Pilatus PC12 45 · Accident: wildlife encounter (non-bird) during takeoff
From Gwinnett County Briscoe Field (LZU) to Pensacola International Airport (PNS)
Event
- NTSB case
- GAA16CA129
- 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
Pilatus PC12 45
- Aircraft type
- Pilatus PC12
- 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
- N338PC
- Operator
- Quest Diagnostics
- Onboard fatalities
- Unknown
- Route
- From Gwinnett County Briscoe Field (LZU), Lawrenceville, GATo Pensacola International Airport (PNS), Pensacola, FL
- Aircraft age
- About 16 years (built 2000)
- 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
- Takeoff
- 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
- Wildlife encounter (non-bird)
- 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 as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The operator reported that during the takeoff roll, at the moment of rotation during night visual conditions, the pilot observed two white-tailed deer (Odocoileus virginianus) running across the runway. The pilot maneuvered the airplane to avoid the deer, however one of the deer impacted the nose wheel. The pilot decided to continue the takeoff, the airplane orbited the airport for about 1.5 hours, and then landed without further incident. A postflight inspection revealed substantial damage to the fuselage.
The operator verified that there were no preimpact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation.
As a safety recommendation, the operator stated that wildlife strikes can be dealt with proactively through accurate reports from the airport users and airport management establishing a program of regular wildlife population control. The operator further stated that reporting wildlife activity is the most important element of this proactive approach and that without these reports airport managers cannot properly gauge the amount of timing of their response.
The operator reported that from a conversation with the airport manager that the deer population has increased on the airport because of hunting pressure in the surrounding areas.
The airport manager reported that all of the movement areas at the airport are fenced. He also reported that the airport fencing is "standard FAA (Federal Aviation Administration) specification 6 foot tall chain link fence with triple strand barbed wire at the top on standard 45 degree angle outriggers."
The FAA has published CERTALERT 04-16 Deer Hazard to Aircraft and Deer Fencing (December 2004). This document describes the deer hazard to aircraft and recommends various airport fencing options to mitigate deer and aircraft strikes. This document states in part:
"Elevated deer populations in the United States represent an increasingly serious threat to both commercial and general aviation aircraft. It is currently estimated that there over 26 million deer in the United States. Because of increasing urbanization and rapidly expanding deer populations, deer are adapting to human environments, especially around airports, where they often find food and shelter.
Proper fencing is the best way of keeping deer off aircraft movement areas. The FAA recommends a 10-12 foot chain link fence with 3-strand barbed wire outriggers. In some cases an airport may be able to use an 8-foot chain link fence with 3-strand barbed wire outriggers, depending upon the amount of deer activity in a local area. All fencing must be properly installed and maintained.
If deer are observed on or near the aircraft movement area, immediate action must be taken to remove them."
The Georgia Department of National Resources Wildlife Resources Division has published White-Tailed Deer Fact Sheet (April 2004). This document describes the behavior patterns of the white-tailed deer and states in part:
"Deer are most active around dawn and dusk. This is called a crepuscular activity pattern."
Probable cause
An unintentional collision with a white-tailed deer during the takeoff roll in night visual conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA16CA129
- Event ID
- 20160216X40423
- Case number
- GAA16CA129
- 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. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2016-01-27.
- API snapshot SHA-256: 1cf2fa248a60d531f6adae39384f052ec4008fb2f31a9ee6a358a461329d683e; retrieved 2026-09-16T03:09:48.065Z.