# NTSB GAA20CA089: Cessna 172, N683SP, DuBois, PA, November 17, 2019 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: November 17, 2019, 17:30 local (22:30 UTC) - Place: DuBois, PA - Coordinates: 41.178333, -78.898612 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=41.1783&lon=-78.8986&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-aborted after touchdown: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report May 21, 2020 - Report: Approved by Office Director - NTSB office: General Aviation Accidents - Parties: FAA - NTSB case key (mKey): 100607 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA20CA089 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/100607/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=100607 - Page: https://openairdocs.org/ntsb/GAA20CA089 ## Probable cause The pilot's improper fuel management, which resulted in fuel starvation and a total loss of engine power, and his subsequent improper landing flare, which resulted in a hard, bounced landing. Contributing to the accident were the pilot's improper preflight inspection during which he failed to see that the right fuel cap was not secured. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Fluids: fuel](https://openairdocs.org/ntsb-findings/01071010): Aircraft › Fluids/misc hardware · Fluid management (probable cause); cases with it: [Cessna 172S, 2 cases](https://openairdocs.org/ntsb-findings/01071010/cases.md?model=2072439), [All aircraft, 1,695 cases](https://openairdocs.org/ntsb-findings/01071010/cases.md) - [Performance/control parameters: landing flare](https://openairdocs.org/ntsb-findings/01062041): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (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) - [Use of equip/info: use of equip/system](https://openairdocs.org/ntsb-findings/02063015): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cessna 172S, 14 cases](https://openairdocs.org/ntsb-findings/02063015/cases.md?model=2072439), [All aircraft, 1,391 cases](https://openairdocs.org/ntsb-findings/02063015/cases.md) - [Inspection: preflight inspection](https://openairdocs.org/ntsb-findings/02061510): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cessna 172S, 2 cases](https://openairdocs.org/ntsb-findings/02061510/cases.md?model=2072439), [All aircraft, 551 cases](https://openairdocs.org/ntsb-findings/02061510/cases.md) - [Action: lack of action](https://openairdocs.org/ntsb-findings/02041030): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Cessna 172S, 14 cases](https://openairdocs.org/ntsb-findings/02041030/cases.md?model=2072439), [All aircraft, 792 cases](https://openairdocs.org/ntsb-findings/02041030/cases.md) - [Use of equip/info: use of checklist](https://openairdocs.org/ntsb-findings/02063030): Personnel issues › Task performance · Pilot; cases with it: [Cessna 172S, 3 cases](https://openairdocs.org/ntsb-findings/02063030/cases.md?model=2072439), [All aircraft, 336 cases](https://openairdocs.org/ntsb-findings/02063030/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Prior to flight: Aircraft inspection event](https://openairdocs.org/ntsb-events/050); cases with it: [Cessna 172S, 1 case](https://openairdocs.org/ntsb-events/050/sequence.md?model=2072439), [All aircraft, 229 cases](https://openairdocs.org/ntsb-events/050/sequence.md) - [Landing-aborted after touchdown: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341) (defining event); cases with it: [Cessna 172S, 19 cases](https://openairdocs.org/ntsb-events/341/sequence.md?model=2072439), [All aircraft, 3,820 cases](https://openairdocs.org/ntsb-events/341/sequence.md) - [Landing-aborted after touchdown: Fuel starvation](https://openairdocs.org/ntsb-events/191); cases with it: [Cessna 172S, 2 cases](https://openairdocs.org/ntsb-events/191/sequence.md?model=2072439), [All aircraft, 733 cases](https://openairdocs.org/ntsb-events/191/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: Hard landing](https://openairdocs.org/ntsb-events/092); 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 pilot reported that the airplane was refueled while he performed the preflight inspection at night. He recalled that the fuel selector had been set to "both," and about halfway through the flight, he noticed that the right fuel tank appeared full but that the left fuel gauge indicated that fuel was being consumed from the left tank. He decided that he would "check the situation " when he reached his destination. About 5 miles from his destination, he noticed that the left-wing tank fuel quantity indicator showed that the left tank had 5 gallons remaining and that the right tank was still full. The pilot stated that, during the approach, the airplane became "very unstable and seemed to be uncoordinated." The stall warning horn sounded, and he applied left aileron and left rudder to align the airplane's heading with the runway heading but was unsuccessful. He aborted the landing, established a climb, and retracted the flaps. The Low Fuel warning light illuminated, and he switched the fuel selector to the right tank. The engine lost power, and he made a right tear drop turn back to the runway. When the airplane was about 1,000 ft above ground level, he pitched for best glide airspeed, about 70 knots, and he attempted to restart the engine to no avail. He lowered the nose, the airspeed increased to 85 knots, and he added 20° of flaps and landed on the runway. The airplane bounced hard and then came to a stop. After the accident, it was determined that the right fuel cap was not secured and had fallen off the airplane onto the runway during takeoff. The airplane sustained substantial damage to the lower fuselage longerons. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. ## Factual narrative The pilot reported that the airplane was refueled while he performed the pre-flight inspection at night, but the right fuel tank fuel cap was not secured. He recalled that the fuel selector had been set to Both, and about halfway through the flight, he noticed that the right fuel tank appeared full, but the left fuel gauge indicated that fuel was being consumed from the left tank. He decided that he would, "check the situation out" when he reached his destination. About 5 miles from his destination, he noticed that the left wing tank fuel quantity indicator showed that the left tank had 5-gallons remaining, and that the right tank was still full. During approach, the airplane became, "very unstable and seemed to be uncoordinated." The stall warning horn sounded, and he applied left aileron and left rudder to align the airplane's heading with the runway heading but was unsuccessful. He aborted the landing, established a climb and retracted the flaps. The Low Fuel warning light illuminated, and he switched the fuel selector to the right tank. The engine lost power, and he made a right tear drop turn back to the runway. The airplane was about 1,000ft above ground level, and he pitched for best glide airspeed about 70 knots, and he attempted to restart the engine, but the engine did not start. He lowered the nose, the airspeed increased to 85 knots and he put in 20° of flaps and landed on the runway. The airplane bounced hard and returned to the runway before coming to a stop. The airplane sustained substantial damage to the lower fuselage longerons. The pilot reported that there were no mechanical malfunctions or failures with the airplane that would have precluded normal operation. ## Aircraft - Registration: [N683SP](https://openairdocs.org/aircraft/N683SP), registered now, S/N 172S8094, built 1999 (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 I0360 series](https://openairdocs.org/engine/lycoming-i0360-series) (registry code 41515, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 172S8094 - Year built: 1999 - Airframe hours: 6938.8 - Engines: Lycoming IO-360-L2A 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Hobart Aviation Inc - Registered owner: Hobart Aviation Inc - Airworthiness certificate: Standard, Normal - Last inspection: 100 hour, October 29, 2019 - Departed: AKR, Akron, OH - Destination: AKR, Akron, OH - Airport: DUJ, Dubois Rgnl, runway 25, 5,503 × 100 ft, asphalt - Equipment: Stall warning system, Electronic flight bag or handheld device, Auto-pilot, ADS-B ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 20; injuries: none; private; airplane ratings: single-engine land; medical: class 1, without waivers/limitations; last flight review October 5, 2019; seat: left; restraint: 3-point; flight hours: 103 total, 48 in this make and model, 18 as pilot in command, 13 in the last 90 days, 7 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 130° at 10 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 36 °F, dew point 25 °F - Altimeter: 30.01 inHg - Observed at: KDUJ ## 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 20191117018489A](https://openairdocs.org/incident/20191117018489A), Nov 17, 2019: Cessna 172S, Dubois, PA, Substantial damage. 11/17/2019 Pilot attempted to land at kduj, on runway 25. With approximately 1000' remaining the aircraft landed. The aircraft sustained severe damage with a… ## Docket (2 files) The files NTSB released with the investigation on February 7, 2020, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=100607. 4.9 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 4.8 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40480384&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Photo (item 2, .PDF, 109 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40480385&FileExtension=.PDF&FileName=Photo-Master.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.