CEN26LA035

NTSB accident investigation · Cessna 172 · Grantsburg, WI · November 5, 2025

Accident · No injuriesClass 4 · LimitedFinal report
Date
November 4, 2025, 18:30 local (Nov 5, 2025, 00:30 UTC)
Place
Grantsburg, WI
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N9490HCessna 172
Defining event
Landing-flare/touchdown: Wildlife encounter (non-bird)
Weather
Visual (VMC) · Night/dark
Status
Completed · report December 11, 2025
Report
Approved by Office Director
Investigation class
Class 4 - Basic report with no Prelim publish
NTSB office
Central Region
Parties
FAA Minneapolis FSDO
FAA report
20251104016669A
Case key
201961

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

The collision with a white-tail deer during the landing in dark night visual conditions.

Findings · 5

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Object/animal/substance: animal(s)/bird(s)Environmental issues › Physical environment · Effect on equipmentCessna 172M: 5 casesAll aircraft: 358 casesProbable cause
Object/animal/substance: animal(s)/bird(s)Environmental issues › Physical environment · Contributed to outcomeCessna 172M: 5 casesAll aircraft: 358 casesProbable cause
Object/animal/substance: animal(s)/bird(s)Environmental issues › Physical environment · Awareness of conditionCessna 172M: 5 casesAll aircraft: 358 casesProbable cause
Object/animal/substance: animal(s)/bird(s)Environmental issues › Physical environment · Ability to respond/compensateCessna 172M: 5 casesAll aircraft: 358 casesProbable cause
Light condition: darkEnvironmental issues › Conditions/weather/phenomena · Awareness of conditionCessna 172M: 8 casesAll aircraft: 448 casesProbable cause

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

Analysis

The pilot reported that the airplane was on final approach to the runway in dark night visual conditions with no moon illumination present. She observed that the airport lighting seemed dim and the area surrounding the runway was not illuminated. When she initiated the landing flare, she observed a white-tailed deer running across the runway from the right to the left. She initiated a go-around; however, the deer impacted the right horizontal stabilizer. During the go-around, she noticed a reduced climb performance and a right yaw, however she was able to safely control the airplane. She decided to divert to a different airport due to the possibility of additional deer being present near the runway or perhaps a dead deer on the runway. The pilot contacted air traffic control and landed at a nearby airport without further incident. The right horizontal stabilizer sustained substantial damage. The pilot reported there were no preimpact mechanical malfunctions or failures with the airframe or the engine that would have precluded normal operation. The current airport entry in the FAA Airport/Facility Directory states in the remarks section, “deer & waterfowl on and invof arpt.” According to the University of Wisconsin, white-tail deer prefer an open forest environment consisting of meadows, woodland clearings and farmland and additionally prefer low light to forage, mainly at sunrise and sunset. The accident occurred about 1 hour and 38 minutes after sunset. The publicly owned airport, which is located next to a 30,000-acre state wildlife area, does not have fencing installed to exclude deer and other mammals, nor is it required to. The FAA has published CertAlert 16-03 Recommended Wildlife Exclusion Fencing and states in part: Proper fencing is the best way of keeping deer and coyotes off aircraft movement areas. The FAA recommends a 10-foot fence with 3-strand barbed wire outriggers.

Aircraft

Registration
N9490H
Reported as
Cessna 172 (M)
Category
Airplane
Serial number
17266177
Built
1975
Airframe hours
2,233
Engine
Lycoming Engines O-320-E2D, 150 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Airworthiness certificate
Standard, Normal
Last inspection
Annual · November 26, 2024 · 177 hours before
Departed
ELO · Ely, MN
Destination
GTG · Grantsburg, MN
Flight plan
IFR
Airport
GTG · Grantsburg Muni, runway 12/30, 2,999 × 60 ft, asphalt
Equipment
Satellite tracking device, ADS-B, Electronic primary flight display, Electronic flight bag or handheld device, Onboard weather

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
23
Injuries
None
Certificates
Flight instructor, Commercial
Airplane ratings
Multi-engine land, Single-engine land
Instrument ratings
Airplane
Medical
Class 3, With waivers/limitations
Last flight review
February 12, 2024
Seat
Right
Restraint
3-point
Flight hours
758 total · 425 in this make and model · 562 as pilot in command · 90 in the last 90 days · 7 in the last 30 days · 4 in the last 24 hours

Weather

Conditions
Visual (VMC) · Night/dark
Wind
110° at 3 knots
Visibility
10 statute miles
Lowest ceiling
6,000 ft overcast
Temperature
54 °F, dew point 25 °F
Altimeter
29.88 inHg
Observed at
KRZN, 12 nm away
METAR
KRZN 050015Z AUTO 11003KT 10SM OVC060 12/M04 A2988 RMK AO2 T01211036

Docket · 8

The files NTSB released with the investigation on December 11, 2025, on NTSB’s docket system: statements, records, photos and specialists’ reports. 4.0 MB in all.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.