# NTSB CEN23LA292: Cessna 172R, N64AF, Burlington, VT, July 5, 2023 - Type: NTSB accident investigation - Classification: Accident · No injuries · Class 4 · Limited · Final report - Date: July 5, 2023, 15:45 local (19:45 UTC) - Place: Burlington, VT · Airport runway - Coordinates: 44.471955, -73.153276 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=44.4720&lon=-73.1533&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: 2 uninjured - Status: Completed - Report: Approved by Office Director - Investigation class: Class 4 - Basic report with no Prelim publish - NTSB office: Central Region - Parties: FAA - NTSB case key (mKey): 192579 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN23LA292 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/192579/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=192579 - Page: https://openairdocs.org/ntsb/CEN23LA292 ## Probable cause The student pilot’s improper landing flare, which resulted in a hard, bounced landing and the flight instructor’s delayed remedial action. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Training: training with equipment](https://openairdocs.org/ntsb-findings/02031530): Personnel issues › Experience/knowledge · Student/instructed pilot (probable cause); cases with it: [Cessna 172R, 1 case](https://openairdocs.org/ntsb-findings/02031530/cases.md?model=2072401), [All aircraft, 32 cases](https://openairdocs.org/ntsb-findings/02031530/cases.md) - [Aircraft](https://openairdocs.org/ntsb-findings/01060000): Aircraft › Aircraft oper/perf/capability · Incorrect use/operation (probable cause); cases with it: [Cessna 172R, 1 case](https://openairdocs.org/ntsb-findings/01060000/cases.md?model=2072401), [All aircraft, 63 cases](https://openairdocs.org/ntsb-findings/01060000/cases.md) - [Environmental issues](https://openairdocs.org/ntsb-findings/03040000): Environmental issues › Task environment · Ability to respond/compensate (probable cause); cases with it: [Cessna 172R, 1 case](https://openairdocs.org/ntsb-findings/03040000/cases.md?model=2072401), [All aircraft, 7 cases](https://openairdocs.org/ntsb-findings/03040000/cases.md) - [Info processing/decision: decision making/judgment](https://openairdocs.org/ntsb-findings/02041520): Personnel issues › Action/decision · Instructor/check pilot (probable cause); cases with it: [Cessna 172R, 15 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md?model=2072401), [All aircraft, 3,098 cases](https://openairdocs.org/ntsb-findings/02041520/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 172R, 34 cases](https://openairdocs.org/ntsb-events/092/sequence.md?model=2072401), [All aircraft, 2,102 cases](https://openairdocs.org/ntsb-events/092/sequence.md) ## Analysis According to the flight instructor, the student pilot was a little high on the final approach for the short field landing, which resulted in a steeper approach. Before touch down, the student decreased the pitch attitude, and there was little to no flare. The airplane landed flat, bounced, then hit the nosewheel first as they touched down and bounced a second time. During the second bounce, both pilots heard a noise, the student felt a vibration in the rudder pedals, and initiated a go-around. The flight instructor assumed control of the airplane during climb out and confirmed there were no anomalies with the rudder system before transferring the controls back to the student. During the next landing, the flight instructor stated that the student flared a little high and the airplane ballooned before touchdown. During the landing roll, the airplane veered to the right and neither pilot was able to maintain directional control. The nose landing gear collapsed as both pilots applied the brakes. The airplane impacted a taxiway light and came to rest on the runway. The airplane sustained substantial damage to the firewall and lower fuselage at the nose landing gear support structure. Based on the pilot’s statements it is likely the nose landing gear was compromised during the first landing attempt. The flight instructor reported that there were no anomalies with the airplane before the first landing. He added that the accident could have been prevented if they had performed a go-around if a stabilized approach was not established. ## Aircraft - Registration: [N64AF](https://openairdocs.org/aircraft/N64AF), registered now, S/N 17280069, built 1997 (OpenAirDocs) - Reported make and model: CESSNA 172R - Registry model: [Cessna 172R](https://openairdocs.org/model/cessna-172r) (registry code 2072401) (OpenAirDocs) - Category: Airplane - Serial number: 17280069 - Year built: 1997 - Airframe hours: 13302.5 - Engines: Lycoming IO-360-L2A 180 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Registered owner: Vermont Flight Academy Inc - Airworthiness certificate: Standard, Normal - Last inspection: Annual, May 31, 2023, 78.3 hours before - Departed: KBTV, South Burlington, VT - Destination: Same as departure - Airport: KBVT, Burlington International Airport, runway 01, 4,112 × 75 ft, asphalt - Equipment: Onboard weather, Electronic primary flight display, Electronic multifunction display, Electronic flight bag or handheld device, ADS-B, Stall warning system ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 20; injuries: none; commercial, flight instructor; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 1, without waivers/limitations; last flight review April 10, 2023; seat: right; restraint: 3-point; flight hours: 261 total, 122 in this make and model, 172 as pilot in command, 25 in the last 90 days, 12 in the last 30 days - Student pilot; age 56; injuries: none; student; medical: class 3, with waivers/limitations; seat: left; restraint: 3-point; flight hours: 81 total, 79 in this make and model, 8 as pilot in command, 16 in the last 90 days, 6 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Visibility: 10 statute miles - Temperature: 91 °F, dew point 66 °F - Altimeter: 29.93 inHg - Observed at: KBTV - METAR: KBTV 051954Z VRB03KT 10SM FEW055 FEW250 33/19 A2993 RMK AO2 SLP133 T03330194 ## 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 20230705006609A](https://openairdocs.org/incident/20230705006609A), Jul 5, 2023: Cessna 172R, Burlington, VT, Substantial damage. On July 05, 2023, at 3:25PM local time, a flight instructor was performing/demonstrating a short field landing with a student pilot at the Burlington Vermont… ## Other investigations on N64AF (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 ATL02LA007](https://openairdocs.org/ntsb/ATL02LA007), Oct 20, 2001: Cessna 172 (N64AF), Kissimmee, FL, substantial damage. Probable cause: See narrative for ATL02LA007A. ## Docket (2 files) The files NTSB released with the investigation on November 16, 2023, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=192579. 55.6 MB in all. - Pilot/operator aircraft accident report, NTSB form 6120.1 (item 1, PDF, 17 pages, 55.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=16276408&FileExtension=pdf&FileName=NTSB%206120.1%20Form_Redacted-Rel.pdf - Photos (item 2, PDF, 3 pages, 200 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=16276418&FileExtension=pdf&FileName=Photo%20Array-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.