# NTSB ERA22LA087: Cessna 172S, N215LP, Hazleton, PA, December 12, 2021

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Class 4 · Limited · Final report
- Date: December 12, 2021, 09:00 local (14:00 UTC)
- Place: Hazleton, PA
- Coordinates: 40.9584, -75.9746
- Nearby events: https://openairdocs.org/map.md?lat=40.9584&lon=-75.9746&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Defining event: [Landing: Landing area overshoot](https://openairdocs.org/ntsb-events/380)
- Highest injury: No injuries
- Injuries: 1 uninjured
- Status: Completed
- Report: Approved by Office Director
- Investigation class: Class 4 - Basic report with no Prelim publish
- NTSB office: Eastern Region Aviation
- Parties: FAA/FSDO
- NTSB case key (mKey): 104410
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA22LA087
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/104410/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=104410
- Page: https://openairdocs.org/ntsb/ERA22LA087

## Probable cause

The pilot’s failure to maintain proper airspeed on approach in tailwind conditions, which resulted in an extended touchdown, bounced landing, and runway excursion.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cessna 172S, 206 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072439), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md)
- [Performance/control parameters: airspeed](https://openairdocs.org/ntsb-findings/01062010): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 172S, 16 cases](https://openairdocs.org/ntsb-findings/01062010/cases.md?model=2072439), [All aircraft, 1,681 cases](https://openairdocs.org/ntsb-findings/01062010/cases.md)
- [Wind: tailwind](https://openairdocs.org/ntsb-findings/03034015): Environmental issues › Conditions/weather/phenomena · Effect on operation; cases with it: [Cessna 172S, 9 cases](https://openairdocs.org/ntsb-findings/03034015/cases.md?model=2072439), [All aircraft, 594 cases](https://openairdocs.org/ntsb-findings/03034015/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Landing: Landing area overshoot](https://openairdocs.org/ntsb-events/380) (defining event); cases with it: [Cessna 172S, 5 cases](https://openairdocs.org/ntsb-events/380/sequence.md?model=2072439), [All aircraft, 400 cases](https://openairdocs.org/ntsb-events/380/sequence.md)
- [Landing: Abnormal runway contact](https://openairdocs.org/ntsb-events/090); cases with it: [Cessna 172S, 77 cases](https://openairdocs.org/ntsb-events/090/sequence.md?model=2072439), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md)
- [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Cessna 172S, 76 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=2072439), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md)

## Analysis

The pilot landed with a tailwind and had a higher-than-normal approach speed. The airplane landed long, bounced, and went off the runway. The airplane struck a taxiway light resulting in substantial damage to the left horizontal stabilizer. The pilot reported that the airplane had no preimpact mechanical malfunctions or failures that would have precluded normal operation.

## Aircraft

- Registration: [N215LP](https://openairdocs.org/aircraft/N215LP), registered now, S/N 172S9215, built 2002 (OpenAirDocs)
- Reported make and model: CESSNA 172S
- 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: 172S9215
- Year built: 2002
- Airframe hours: 9769.3
- Engines: Lycoming I0-360-L2A 180 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Operator: Infinity Flight Group
- Registered owner: Christiansen Aviation Inc
- Airworthiness certificate: Standard, Normal
- Last inspection: 100 hour, November 30, 2021
- Departed: TTN, Trenton, NJ
- Destination: Same as departure
- Airport: HZL, Hazleton Rgnl, runway 10, 5,001 × 100 ft, asphalt
- Equipment: Stall warning system, Electronic flight bag or handheld device, ADS-B

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 22; injuries: none; commercial; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 1, without waivers/limitations; last flight review March 20, 2021; seat: left; restraint: 3-point; flight hours: 326.4 total, 248.7 in this make and model

## Weather

- Conditions: Visual (VMC), Day
- Wind: 290° at 7 knots
- Visibility: 10 statute miles
- Temperature: 32 °F, dew point 23 °F
- Altimeter: 30.11 inHg
- Observed at: HZL
- METAR: SA	12/12/2021 14:15->	
METAR KHZL 121415Z AUTO 29007KT 10SM SCT038 02/M05 A3011

## 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 20211212021019A](https://openairdocs.org/incident/20211212021019A), Dec 12, 2021: Cessna 172S, Hazleton, PA, Substantial damage. 12/12/2021, At approximately 09:00 EST, hazelton regional airport (hzl), a CE-172S, N215LP, struck a runway end light while executing a go around on runway 10.…

## Docket (6 files)

The files NTSB released with the investigation on January 25, 2022, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=104410. 12.2 MB in all.

- Pilot/operator aircraft accident report, NTSB form 6120.1 (item 1, PDF, 9 pages, 660 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13085244&FileExtension=pdf&FileName=NTSB%20Report_Redacted-Rel.pdf
- NTSB summary of email statement - DPE to NTSB (item 2, PDF, 1 page, 289 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13099920&FileExtension=pdf&FileName=Summary%20of%20Statement%20-%20DPE-Rel.pdf
- Photos of airplane after accident (item 3, PDF, 2 pages, 2 photos, 657 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13098986&FileExtension=pdf&FileName=Photo%20Array%202-Rel.pdf
- Photos of damage (item 4, PDF, 2 pages, 2 photos, 757 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13085264&FileExtension=pdf&FileName=Photo%20Array-Rel.pdf
- Cell phone video 1 (item 5, MOV, 3.9 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13085407&FileExtension=mov&FileName=Video%201st%20Approach-Rel.mov
- Cell phone video 2 (item 6, MOV, 6.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13085550&FileExtension=mov&FileName=Video%202nd%20Approach-Rel.mov

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.
