# Accident 20211121019719A: Cessna 172P, Wheeling, IL, November 21, 2021

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: November 21, 2021, 11:02 local time
- Place: Wheeling, IL
- Damage: Substantial damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 42.1224° N, 87.9067° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=42.1224&lon=-87.9067&mi=10
- Aircraft: N99715, registered now (https://openairdocs.org/aircraft/N99715) (OpenAirDocs)
- Registry model: Cessna 172P (registry code 2072436, https://openairdocs.org/model/cessna-172p) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172P
- Reported engine: LYCOMING 0-320 SERIES
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Student
- Pilot flight hours: 84 total, 12 in this make and model, 1 in the last 90 days
- NTSB investigation: [NTSB CEN22LA043](https://openairdocs.org/ntsb/CEN22LA043) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20211121019719A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

NTSB ACCIDENT NUMBER IS: CEN22LA043

ATQA ACCIDENT NUMBER FOR THIS EVENT IS: AGL0322001

SAS ACTIVITY NUMBER(S) ASSOCIATED WITH THE EVENT GL03202203357

AIRCRAFT: N99715, S/N 17276501

WHEN: 11/21/2021 1702Z,

WHERE: CHICAGO EXECUTIVE AIRPORT (PWK)

WEATHER CONDITIONS: KPWK 211652Z 23007KT 10SM BKN060 BKN075 10/01 A3001, WINDS FORECASTED TO INCREASE.

INJURIES: NONE

DAMAGE FROM EVENT: SUBSTANTIAL AIRCRAFT DAMAGE. NOSE GEAR ABSORBED MUCH OF THE IMPACT AND SHEARED AWAY BENDING THE FIREWALL CAUSING ENGINE MOUNTS TO BEND AND DAMAGE TO PROPELLER AND SPINNER. LEFT WING STRUCK THE GROUND AND CAUSED DAMAGE AND BUCKLING TO THE LAST THIRD OF THE WING. MINOR AIRPORT FACILITY DAMAGE WITH THE LOSS OF A RUNWAY LIGHT.

POST EVENT FIRE OR DAMAGE: NONE

FLIGHT CONTROL CONTINUITY CHECK: NOMINAL

A STUDENT PILOT WAS COMPLETING SOLO FULL STOP TAKEOFFS AND LANDINGS AT PWK. PILOT HAD TAKEN OFF FROM RUNWAY 24, AND CHANGED TO RUNWAY 16 FOR LANDING. THE PILOT REPORTED SETTING UP ON A LONG 3 MILE FINAL DUE TO PREVIOUS TRAFFIC. PILOT REPORTED A STABILIZED APPROACH WITH HALF FLAPS AND INCREASED SPEED IN ORDER TO BE READY FOR AN EXPECTED CROSSWIND INCREASE IN THE FORECAST. THE PILOT REPORTED BEING PUSHED OFF CENTERLINE BY A SUDDEN CROSSWIND GUST AND EXTENDED THE LANDING APPROACH IN ORDER TO GIVE TIME TO REGAIN ALIGNMENT WITH THE CENTERLINE. THE PILOT REPORTED THAT HE MAY HAVE FLARED TOO HIGH, AND THE AIRCRAFT DROPPED SUDDENLY ON THE LANDING GEAR AND BOUNCED. THIS CHAIN OF EVENTS STARTED A PORPOISED LANDING SCENARIO. SUBSEQUENT BOUNCES BECAME MORE AGGRESSIVE AND ON THE THIRD BOUNCE THE AIRCRAFT VEERED OFF THE RUNWAY IN A LATERAL RUNWAY EXCURSION. THE SPINNER, PROPELLER, AND NOSE OF THE AIRCRAFT IMPACTED THE GRASS JUST EAST OF THE RUNWAY, ABSORBED MUCH OF THE IMPACT AND SLOWED THE AIRCRAFT DOWN. THE LEFT WING IMPACTED THE GROUND AND BROUGHT THE AIRCRAFT TO A STOP. VIDEO FROM THE AIRPORT AUTHORITY SHOWS MUCH OF THE EVENT. THE VIDEO DEPICTS THAT ON THE FIRST BOUNCE THE AIRCRAFT STRUCK NOSE GEAR FIRST. THE PILOT DID NOT INITIATE A GO-AROUND AFTER THE FIRST BOUNCE, AND STRUCK THE RUNWAY HARDER THE SECOND AND THIRD TIME.

## The NTSB's investigation of this event (1)

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.

- [NTSB CEN22LA043](https://openairdocs.org/ntsb/CEN22LA043), Nov 21, 2021: Cessna 172P (N99715), Wheeling, IL, substantial damage. Probable cause: The student pilot’s improper landing flare, which resulted in a hard landing. Contributing was the student pilot’s self-induced pressure to land after being admonished by the controller.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
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.