# NTSB SEA04LA096: Cessna 172M, N5440H, Vernonia, OR, May 29, 2004 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: May 29, 2004, 10:05 local (17:05 UTC) - Place: Vernonia, OR - Coordinates: 45.8525, -123.238891 - Nearby events: https://openairdocs.org/map.md?lat=45.8525&lon=-123.2389&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report January 24, 2005 - Report: Approved by Office Director - Parties: Portland FSDO - NTSB case key (mKey): 59360 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=SEA04LA096 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/59360/pdf - Page: https://openairdocs.org/ntsb/SEA04LA096 ## Probable cause The instructor pilot's misjudgment of speed and distance and his failure to execute a go-around resulting in an overrun of the runway. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Overrun, landing - emergency procedure - simulated, pilot in command - distance/speed - misjudged, pilot in command (cause) - go-around - not performed, pilot in command (cause) - On ground/water encounter with terrain/water, landing - roll - terrain condition - grass (contributing factor) - terrain condition - wet (contributing factor) - On ground/water collision with object, landing - roll - object - fence post (contributing factor) ## Analysis The instructor pilot, who was performing a simulated engine out forced landing as a demonstration for his student, allowed the aircraft's airspeed to remain too fast while on final approach to the 2,940 foot grass strip. Because the airspeed was faster than he desired, during the flare, the aircraft began to float further down the runway than where he had planned to touch down. The instructor pilot was unable to get the aircraft to touch down until approximately 1,000 feet down the runway. After touchdown on the wet grass, he attempted to stop the aircraft before it reached the end of the runway, but he was unable to do so before the aircraft went off the far end. After departing the runway, the aircraft collided with a nearby fence post. ## Factual narrative On May 29, 2004, at 1005 Pacific daylight time, a Cessna 172M, N5440H, impacted a fence post after departing the end of a turf/grass runway during a simulated forced landing at Vernonia Municipal Airport, Vernonia, Oregon. The certified flight instructor and his student were not injured, but the aircraft, which is owned and operated by Twin Oaks Airpark, sustained substantial damage. The 14 CFR Part 91 instructional flight, which departed Starks Twin Oaks Airpark one hour earlier, was being operated in visual meteorological conditions. No flight plan had been filed. There was no report of an ELT activation. According to the instructor pilot, who failed to submit a NTSB Form 6120.1/2, he was performing a simulated engine out forced landing as a demonstration for his student. As he neared the approach end of the 2,940 foot grass strip, the aircraft's airspeed was faster than he desired, and during the flare, it began to float further down the runway than where he had planned to touch down. He said that because of the excess airspeed, he was unable to get the aircraft to touch down until approximately 1,000 feet down the runway. After touchdown, he attempted to stop the aircraft before it reached the end of the runway, but since he had landed on the wet grass, he was unable to get it stopped before the aircraft went off the far end. After departing the runway, the aircraft collided with a nearby fence post. ## Aircraft - Registration: [N5440H](https://openairdocs.org/deregistered/N5440H-2017-09-27), registration cancelled 2017-09-27, S/N 17265438, built 1975 (OpenAirDocs) - Reported make and model: Cessna 172M - Registry model: [Cessna 172M](https://openairdocs.org/model/cessna-172m) (registry code 2072418) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17265438 - Airframe hours: 9406 - Engines: Lycoming O-320-E2D 150 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Registered owner: Twin Oaks Airpark - Airworthiness certificate: Standard, Normal - Last inspection: 100 hour, April 4, 2004 - Departed: 7S3, Twin Oaks A/P, OR - Destination: 05S, Vernonia, OR - Airport: 05S, Vernonia Municipal, runway 27, 2,940 × 45 ft, grass/turf ## Flight crew As NTSB recorded them. NTSB leaves out names. - Flight instructor; age 38; injuries: none; flight instructor, commercial; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 2, valid medical--w/ waivers/lim; seat: right; flight hours: 400 total - Student pilot; age 57; injuries: none; student; medical: class 3, valid medical--no waivers/lim.; seat: left; flight hours: 30 total ## Weather - Conditions: Visual (VMC), Day - Wind: 160° at 5 knots - Visibility: 10 statute miles - Lowest ceiling: 3,000 ft broken - Temperature: 55 °F ## 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 20040529009009A](https://openairdocs.org/incident/20040529009009A), May 29, 2004: Cessna 172M, Vernonia, OR, Substantial damage. (-23) On 05-29-04, N5440H a Cessna CE-172 landed fast on rwy 260 at Vernonia, OR (05S) and ran off the end of the wet grass strip. Due to the wet grass the… ## Other investigations on N5440H (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 GAA17CA186](https://openairdocs.org/ntsb/GAA17CA186), Mar 12, 2017: Cessna 172 (N5440H), Hillsboro, OR, substantial damage. Probable cause: The pilot's failure to maintain directional control during the landing roll in quartering tailwind conditions. 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.