# NTSB ERA17LA026: Cessna 172, N497SJ, Fort Lauderdale, FL, October 1, 2016 - Type: NTSB accident investigation - Classification: Accident · No injuries · Class 3 · Limited · Final report - Date: October 1, 2016, 18:08 local (22:08 UTC) - Place: Fort Lauderdale, FL · Runway 9 - Coordinates: 26.197221, -80.170829 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=26.1972&lon=-80.1708&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed - Report: Approved by Office Director - Investigation class: Class 3 - NTSB office: Eastern Region Aviation - Parties: FXE Flight Center Corp., FAA FSDO - NTSB case key (mKey): 94257 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA17LA026 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/94257/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=94257 - Page: https://openairdocs.org/ntsb/ERA17LA026 ## Probable cause The pilot’s improper landing flare in gusting crosswind conditions, which resulted in a nose landing gear collapse. ## 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) - [Wind: crosswind](https://openairdocs.org/ntsb-findings/03034040): Environmental issues › Conditions/weather/phenomena · Response/compensation (probable cause); cases with it: [Cessna 172S, 18 cases](https://openairdocs.org/ntsb-findings/03034040/cases.md?model=2072439), [All aircraft, 1,008 cases](https://openairdocs.org/ntsb-findings/03034040/cases.md) - [Engine (reciprocating): recip eng oil sys](https://openairdocs.org/ntsb-findings/01058550): Aircraft › Aircraft power plant · Failure; cases with it: [Cessna 172S, 1 case](https://openairdocs.org/ntsb-findings/01058550/cases.md?model=2072439), [All aircraft, 130 cases](https://openairdocs.org/ntsb-findings/01058550/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Enroute-climb to cruise: Powerplant sys/comp malf/fail](https://openairdocs.org/ntsb-events/340); cases with it: [Cessna 172S, 3 cases](https://openairdocs.org/ntsb-events/340/sequence.md?model=2072439), [All aircraft, 820 cases](https://openairdocs.org/ntsb-events/340/sequence.md) - [Approach: Powerplant sys/comp malf/fail](https://openairdocs.org/ntsb-events/340); cases with it: [Cessna 172S, 3 cases](https://openairdocs.org/ntsb-events/340/sequence.md?model=2072439), [All aircraft, 820 cases](https://openairdocs.org/ntsb-events/340/sequence.md) - [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090) (defining event); 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-flare/touchdown: 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) - [Landing-flare/touchdown: Landing gear collapse](https://openairdocs.org/ntsb-events/094); cases with it: [Cessna 172S, 21 cases](https://openairdocs.org/ntsb-events/094/sequence.md?model=2072439), [All aircraft, 1,787 cases](https://openairdocs.org/ntsb-events/094/sequence.md) ## Analysis Shortly after departing on the local flight, the pilot noticed that the engine oil temperature indicated 245°, or redline, and the engine began to run roughly. The pilot contacted air traffic control and requested to return to the airport. The controller cleared the pilot to land and advised of the wind conditions. Upon touchdown, the airplane bounced and came to rest on the runway, resulting in substantial damage. On-scene examination revealed damage consistent with the airplane impacting the runway on the nose landing gear. Examination of the engine revealed that the vernatherm had failed, which would have resulted in elevated engine oil temperature; however, there were no other engine anomalies that would have precluded normal operation. The conditions at the time of the accident included a 50° crosswind between 7 and 14 knots. The airplane's published maximum crosswind component was 15 knots. The circumstances of the accident are consistent with the pilot's improper landing flare while landing in gusting, crosswind conditions, which resulted in the nose landing gear contacting the runway and its subsequent collapse. ## Factual narrative On October 1, 2016, about 1808 eastern daylight time, a Cessna 172S airplane, N497SJ, was substantially damaged when it was involved in an accident near Fort Lauderdale, Florida. The pilot and passenger were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot's preflight inspection revealed no anomalies, and he determined that the engine contained 7 quarts of oil. He taxied to the runway, completed an engine run-up, and was cleared for takeoff. The pilot applied full throttle and checked that all engine instruments were in the "green arc," including oil temperature and oil pressure. At 2,500 feet mean sea level (msl) and 5 nautical miles northwest of the departure airport, the pilot noticed the oil temperature indicated 245°, or redline. The pilot contacted air traffic control and requested to return to the airport; shortly thereafter, the engine began running roughly. The tower controller cleared the pilot for landing, and upon touchdown, the airplane bounced and came to rest on the runway. The pilot stated that he did not go around or abort the landing because of the potential engine issue. On-scene examination of the airplane by a Federal Aviation Administration (FAA) inspector revealed that the airplane contacted the runway on the nose landing gear, which was bent forward and had collapsed into the firewall. The propeller struck the runway, damaging both propeller tips. Oil was seeping from both sides of the engine cowling, both of the access doors on the cowling, and from underneath the cowling. The engine oil quantity dipstick indicated that about 3 quarts of oil remained in the engine. The oil appeared clear and free of contamination. Examination of the engine under supervision from an FAA inspector revealed no hidden damage; however, the vernatherm, would not close. The vernatherm is a thermostatic oil cooler bypass valve which allows cold engine oil to bypass the oil cooler, then closes when the oil temperature reaches about 180°F, forcing the engine oil to pass through the oil cooler. Review of air traffic control audio recordings revealed that, when providing the landing clearance, the tower controller advised the pilot that the wind was from 080° at 9 knots gusting to 18 knots, which would have resulted in a 50° left crosswind component of between 7 and 14 knots for the landing runway. According to the Cessna 172S Pilot’s Operating Handbook, the maximum demonstrated crosswind velocity was 15 knots. ## Aircraft - Registration: [N497SJ](https://openairdocs.org/aircraft/N497SJ), registered now, S/N 172S8497, built 2000 (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 I0-360-B1E](https://openairdocs.org/engine/lycoming-i0-360-b1e) (registry code 41559, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 172S8497 - Year built: 2000 - Airframe hours: 2410.8 - Engines: LYCOMING IO-360-L2A 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Fxe Flight Center Corp - Registered owner: Fxe Flight Center Corp - Airworthiness certificate: Standard, Normal - Last inspection: 100 hour, September 23, 2016 - Departed: FXE, Fort Lauderdale, FL - Destination: PGD, Punta Gorda, FL - Flight plan: Unknown - Airport: FXE, Fort Lauderdale Executive, runway 09, 6,002 × 100 ft, asphalt - Equipment: Auto-pilot, Stall warning system ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 45; injuries: none; flight instructor, commercial; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 2, with waivers/limitations; last flight review September 3, 2016; seat: left; restraint: 3-point; flight hours: 722 total, 483 in this make and model, 606 as pilot in command, 66 in the last 90 days, 6 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 70° at 7 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 84 °F, dew point 72 °F - Altimeter: 29.95 inHg - Observed at: FXE ## 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 20161001016109A](https://openairdocs.org/incident/20161001016109A), Oct 1, 2016: Cessna 172S, Fort Lauderdale, FL, Substantial damage. Aircraft N497SJ with one pilot and one passenger on board, took off from Fort Lauderdale executive airport (fxe) flying to punta gorda airport (pgd), FL when… ## Other investigations on N497SJ (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 ERA25LA072](https://openairdocs.org/ntsb/ERA25LA072), Dec 9, 2024: Cessna 172 (N497SJ), Pahokee, FL, substantial damage. Probable cause: The pilots' failure to see and avoid the other airplane, which resulted in a midair collision during short final approach. - [NTSB GAA18CA348](https://openairdocs.org/ntsb/GAA18CA348), May 29, 2018: Cessna 172 (N497SJ), Orlando, FL, substantial damage. Probable cause: The pilot’s improper landing flare, which resulted in a bounced, hard landing. - [NTSB FTW02LA068](https://openairdocs.org/ntsb/FTW02LA068), Jan 12, 2002: Cessna 172S (N497SJ), Sugar Land, TX, substantial damage. Probable cause: the student pilot's failure to maintain directional control during landing. ## Docket (9 files) The files NTSB released with the investigation on April 19, 2021, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=94257. 29.6 MB in all. - Pilot/operator aircraft accident report, NTSB form 6120.1 (item 1, PDF, 10 pages, 14.8 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=11946106&FileExtension=pdf&FileName=NTSB%20Form%206120_Redacted-Rel.pdf - Pilot statement (item 2, PDF, 1 page, 152 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=11944365&FileExtension=pdf&FileName=Pilot%20Statement-Rel.pdf - Excerpt from Cessna 172S POH - crosswind landing (item 3, PDF, 1 page, 146 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=11944075&FileExtension=pdf&FileName=Excerpt%20from%20Cessna%20172S%20POH%20-%20Crosswind%20Landing-Rel.pdf - N497SJ - kfxe audio recording (approach and landing) (item 4, MP3, 3.8 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=11946934&FileExtension=mp3&FileName=KFXE-Twr1-Oct-01-2016-2200Z-Rel.mp3 - Photo array (item 5, PDF, 11 pages, 9.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=11943151&FileExtension=pdf&FileName=Photo%20Array-Rel.pdf - Kfxe - airport diagram (item 6, PDF, 1 page, 76 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=11944085&FileExtension=pdf&FileName=KFXE%20-%20Airport%20Diagram-Rel.pdf - Memorandum for record - airplane and engine examinations (item 7, PDF, 1 page, 149 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=11948511&FileExtension=pdf&FileName=MEMORANDUM%20FOR%20RECORD-Rel.pdf - Post accident damage assessment (item 8, PDF, 1 page, 107 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=11944759&FileExtension=pdf&FileName=Post%20Accident%20Damage%20Assessment_Redacted-Rel.pdf - Statement of party representatives to NTSB investigation (item 9, PDF, 1 page, 1.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=11944796&FileExtension=pdf&FileName=Party%20Form_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.