# NTSB CEN21LA066: Cessna 172, N99HV, Lawrence, KS, November 20, 2020

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Class 3 · Limited · Final report
- Date: November 20, 2020, 14:50 local (20:50 UTC)
- Place: Lawrence, KS
- Coordinates: 39.009273, -95.212902 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=39.0093&lon=-95.2129&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Defining event: [Landing-flare/touchdown: Hard landing](https://openairdocs.org/ntsb-events/092)
- Highest injury: No injuries
- Injuries: 1 uninjured
- Status: Completed
- Report: Approved by Office Director
- Investigation class: Class 3
- NTSB office: Central Region
- Parties: FAA Flight Standards
- NTSB case key (mKey): 102336
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN21LA066
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/102336/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=102336
- Page: https://openairdocs.org/ntsb/CEN21LA066

## Probable cause

The student pilot’s improper landing flare/touchdown which resulted in a hard landing.

## 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 · Student/instructed 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: landing flare](https://openairdocs.org/ntsb-findings/01062041): Aircraft › Aircraft oper/perf/capability · Incorrect use/operation (probable cause); cases with it: [Cessna 172S, 99 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md?model=2072439), [All aircraft, 1,285 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md)

## Sequence of events

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

- [Landing-flare/touchdown: Hard landing](https://openairdocs.org/ntsb-events/092) (defining event); cases with it: [Cessna 172S, 102 cases](https://openairdocs.org/ntsb-events/092/sequence.md?model=2072439), [All aircraft, 2,102 cases](https://openairdocs.org/ntsb-events/092/sequence.md)

## Analysis

The student pilot planned on a solo flight and reported that he didn't notice anything unusual during the pre-fight inspection. Before takeoff, he manipulated the control yoke through its full range of motion and did not notice any abnormalities. The student pilot reported that during the first takeoff, the nose pitched up and airplane climbed much faster than expected which he attributed to the weight difference from flying solo rather than with an instructor in the airplane. He stayed in the traffic pattern and stated he was centered on the runway and pulled back on the yoke for the flare. The yoke suddenly came back, and the nose pitched very high. The student pilot added that he didn't expect this sudden pitch change and prepared to add full throttle for a go-around when the airplane stalled and landed hard. After landing the student pilot moved the yoke through the full range forward and backward to check the functionality. He stated that he did not notice the same "pop" forward and backward like he did during the previous landing, so he taxied back for another takeoff. The student pilot again reported that during the second flight it was very difficult to control the pitch and airspeed and the yoke seemed to push either forward or backward over some type of "stuck" point, so he selected full flaps on final. After he initiated the landing flare, there was again a noticeable "snap" back of an inch or two of the control yoke. The main gear landed first, however; the nose wheel came down very fast. Examination of the airplane found damage to the airplane’s nose gear and substantial damage to the firewall and fuselage. There were no abnormities that would indicate the damage was present before the student’s hard landings and the damage to the structure and flight controls are likely due to the student’s two hard landings.

## Factual narrative

On November 20, 2020, about 1450 central standard time, a Cessna 172S airplane, N99HV, was substantially damaged when it was involved in an accident near Lawrence, Kansas. The student pilot was not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 instructional flight. According to the student pilot, he planned a solo flight. The instructor checked out the airplane from the flight school and passed it off to the student. The instructor indicated that although he would be with another student, he would still be available on the radio if the student needed anything. The student pilot reported that he didn't notice anything unusual during the pre-fight inspection and proceeded through the checklist for obtaining weather and runway information. The student pilot added that that he finished the engine runup and magneto checks and manipulated the control yoke through its full range of motion. The student pilot reported that during the first takeoff the nose pitched up and the airplane climbed much faster than expected, which he attributed to the weight difference from flying solo rather than with an instructor in the airplane. He added that it felt like he had to apply a lot of forward pressure on the yoke to keep the nose down, more than he was used to. He double checked the trim wheel, adding that it felt like it was out of trim, but the wheel was where he set it during the pre-flight. The student pilot stayed in the traffic pattern and on final he reduced the throttle and prepared to land. He stated he was centered on the runway and pulled back on the yoke for the flare. The yoke suddenly came back, and the nose pitched very high. The student pilot added that he didn't expect this sudden pitch change and prepared to add full throttle for a go-around when the airplane stalled and landed hard. After landing the student pilot moved the yoke through the full range forward and backward to check the functionality. He stated that he did not notice the same "pop" forward and backward like he did during the previous landing, so he taxied back for another takeoff. He stated that during the initial climb there was a noticeable change in the yoke pressure, and it was difficult to apply enough forward pressure to keep the nose down. He then turned from base to final and lined up for the landing. The student pilot again reported that it was very difficult to control the pitch and airspeed and the yoke seemed to push either forward or backward over some type of "stuck" point, so he selected full flaps on final. After he initiated the landing flare, there was again a noticeable "snap" back of an inch or two of the yoke. The main gear landed first, however; the nose wheel came down very fast. The student pilot reported that the yoke was as far back as it he could hold it, but the airplane didn't seem to respond to the control input. An initial inspection of the airplane noted damage to the airplane’s nose gear and substantialdamage to the firewall and fuselage. An additional examination of the airplane found damage to the forward fuselage structure. Elevator control movement was limited and there was impact damage to the airplane’s tunnel structure and control yoke guides, which jammed the elevator controls. Additional damage was found to the airplane’s landing gear which included the nose gear being tilted 15-degrees. There were no abnormities that would indicate the damage was present before the student’s hard landings.

## Aircraft

- Registration: [N99HV](https://openairdocs.org/aircraft/N99HV), registered now, S/N 172S10090, built 2005 (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: 172S10090
- Airframe hours: 7843.9
- Engines: Lycoming IO-360-L2A reciprocating
- Damage: Substantial damage
- Flight: Instructional, Part 91
- Operator: Aerohawk LLC
- Registered owner: Aerohawk LLC
- Airworthiness certificate: Standard, Utility; Standard, Normal
- Last inspection: 100 hour, October 21, 2020
- Departed: LWC, Lawrence, KS
- Airport: LWC, Lawrence Municipal

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Student pilot; injuries: none; student; medical: class 3, without waivers/limitations; seat: left; flight hours: 19 total, 19 in this make and model

## Weather

- Conditions: Visual (VMC), Day
- Wind: 70° at 8 knots
- Visibility: 10 statute miles
- Lowest ceiling: 9,000 ft broken
- Temperature: 61 °F, dew point 39 °F
- Altimeter: 30.31 inHg
- Observed at: KLWC

## 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 20201120018579A](https://openairdocs.org/incident/20201120018579A), Nov 20, 2020: Cessna 172S, Lawrence, KS, Substantial damage. The aircraft departed from Lawrence, KS (lwc) for a student pilot solo flight. After approach back to lwc, the student pilot reported a hard landing. The…

## Other investigations on N99HV (3)

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 GAA17CA351](https://openairdocs.org/ntsb/GAA17CA351), Jun 10, 2017: Cessna 172 (N99HV), Lawrence, KS, substantial damage. Probable cause: The student pilot's incorrect control application during landing after a simulated engine failure, which resulted in a hard, bounced landing, and the flight instructor's delayed action to perform a…
- [NTSB CEN11CA100](https://openairdocs.org/ntsb/CEN11CA100), Dec 7, 2010: Cessna 172S (N99HV), Lawrence, KS, substantial damage. Probable cause: The student pilot’s non-stabilized approach and improper landing flare, which resulted in a hard landing.
- [NTSB CEN10CA163](https://openairdocs.org/ntsb/CEN10CA163), Mar 10, 2010: Cessna 172S (N99HV), Lawrence, KS, substantial damage. Probable cause: The student pilot's failure to maintain an appropriate glide path during approach. Contributing to the accident was the student pilot's decision to continue the approach instead of going around.

## Docket (4 files)

The files NTSB released with the investigation on December 10, 2021, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=102336. 2.6 MB in all.

- Pilot statement (item 1, PDF, 2 pages, 425 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=11782886&FileExtension=pdf&FileName=Pilot%20Statement_Redacted-Rel.pdf
- Hard landing inspection (item 2, PDF, 11 pages, 2.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=11782896&FileExtension=pdf&FileName=N99HV%20Hard%20Landing%20Inspection%20-%20Maintenance-Rel.pdf
- Inspection letter (item 3, PDF, 1 page, 93 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=11783099&FileExtension=pdf&FileName=N99HV%20Hard%20Landing%20Inspection%20-%20Inspection%20Letter_Redacted-Rel.pdf
- Maintenance statement (item 4, PDF, 1 page, 78 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=11783212&FileExtension=pdf&FileName=Mx%20Statement_Redacted-Rel.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.
