# NTSB IAD05LA087: Cessna 172M, N80802, Marysville, OH, June 26, 2005 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: June 26, 2005, 10:50 local (14:50 UTC) - Place: Marysville, OH - Coordinates: 40.224723, -83.351669 - Nearby events: https://openairdocs.org/map.md?lat=40.2247&lon=-83.3517&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report February 28, 2006 - Report: Approved by Office Director - Parties: FAA FSDO-07 - NTSB case key (mKey): 61820 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=IAD05LA087 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/61820/pdf - Page: https://openairdocs.org/ntsb/IAD05LA087 ## Probable cause The pilot's failure to maintain directional control during landing. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Loss of control - on ground/water, landing - flare/touchdown - directional control - not maintained, pilot in command (cause) - On ground/water collision with object, landing - aborted - object - airport sign/marker ## Analysis As the airplane crossed the runway threshold, the pilot leveled the pitch attitude, and then began to flare for landing. The airplane touched down, about 1,500 feet from the runway threshold, "veered" to the right, and crossed over grass next to the runway, towards a crowd of people. The pilot then decided to abort the landing. During the aborted landing the airplane came into contact with a runway edge light, a direction sign for the runway exit ,and a taxiway location sign. Following the initial climb, he determined that the elevator was jammed; however, he was able to control the altitude of the airplane by adding power to climb and reducing power to descend. After gaining control, he declared an emergency. The final approach, flare, and landing were uneventful. ## Factual narrative On June 26, 2005, about 1050 eastern daylight time, a Cessna 172M, N80802, was substantially damaged during an aborted landing at Union County Airport (MRT), Marysville, Ohio. The certificated private pilot and passenger were not injured. Visual meteorological conditions prevailed, and no flight plan was filed for the personal flight, which originated at Bluffton Airport (5G7), Bluffton, Ohio and was conducted under 14 CFR part 91. According to written and verbal statements provided by the pilot, after arriving in the vicinity of Marysville, he entered a right traffic pattern for runway 27, in order to avoid an aerobatic competition that was being held on the opposite side of the runway. While on the final leg of the traffic pattern, he extended the flaps to 20 degrees and reduced engine power. As he crossed the runway threshold, he leveled the airplane, and held that attitude for about 1,500 feet. He then flared for landing. As the airplane touched down, it "veered" to the right, and he attempted to compensate. The airplane then crossed over grass next to the runway, towards a crowd that was observing the aerobatic competition. The pilot then decided to abort the landing. After adding full power, disengaging the carburetor heat, and increasing the airplane's pitch attitude, the right horizontal stabilizer came into contact with a taxiway sign. The sign was located approximately half way down the side of a taxiway that paralleled runway 27. Assuming that the landing gear had made contact with the sign, the pilot continued his climb, which became uncontrollable, and the stall warning began to sound. While attempting to level the airplane about 1,200 feet above mean sea level, the pilot realized that the stabilizer had contacted the sign, and not the landing gear. After gaining control of the airplane, he declared an emergency, and transmitted on the common traffic advisory frequency that he was going to make a left crosswind turn for runway 27. As he made his left turn, he requested that the "aerobatics box" be cleared, and he continued his approach for the runway. As the pilot assessed the situation, he determined that elevator was jammed; however, he was able to control the altitude of the airplane by adding power to climb or by reducing power to descend. He then added power to climb to 2,000 feet msl, turned a left downwind for runway 27, and began his preparation for an emergency landing. At a point abeam the "numbers" for runway 27, he reduced power, and started his descent. He made normal radio position calls making note of his emergency. The final approach, flare, and landing were uneventful. The Union County Airport Authority conducted an inspection of the area around the parallel taxiway for runway 27, and found that the airplane had struck and destroyed a runway edge light, a direction sign for the runway exit, and a taxiway location sign. No tire marks or ground scarring were noted on the asphalt for runway 27, the parallel taxiway, or the surrounding turf covered areas. A postaccident inspection by an airframe and powerplant mechanic revealed wrinkling of the skin on the right horizontal stabilizer along with impact damage to the tip and leading edge. Compression buckling was evident on the left side and lower skin of the aft fuselage, and the bulkhead just forward of the tailcone was damaged. The pilot held a private pilot certificate with airplane single-engine-land and instrument ratings. His most recent Federal Aviation Administration first-class medical certificate was issued on June 16, 2005. He reported 92.3 total hours of flight experience. A weather observation taken at Ohio State University Airport (OSU), located about 15 nautical miles south east, at 1053, reported calm winds, visibility 5 statute miles in haze, sky conditions clear below 12,000 feet, temperature 81 degrees Fahrenheit, dew point 69 degrees Fahrenheit and an altimeter setting of 30.15 inches of mercury. ## Aircraft - Registration: [N80802](https://openairdocs.org/deregistered/N80802-2013-05-13), registration cancelled 2013-05-13, S/N 17266753, built 1976 (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: 17266753 - Airframe hours: 2477.7 - Engines: Lycoming O-320-E2D 150 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Operator: Prime Aero Inc. - Registered owner: Lawson Aviation LLC. - Airworthiness certificate: Standard, Normal - Last inspection: Continuous airworthiness, June 1, 2005, 31.2 hours before - Departed: 5G7, Bluffton, OH - Destination: MRT, Marysville, OH - Airport: MRT, Union County Airport, runway 27, 4,218 × 75 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 41; injuries: none; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, with waivers/limitations; last flight review November 1, 2003; seat: left; flight hours: 92 total, 79 in this make and model, 31 as pilot in command, 10 in the last 90 days, 10 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 0° at 0 knots - Visibility: 5 statute miles - Temperature: 81 °F, dew point 70 °F - Altimeter: 30.14 inHg - Observed at: OSU, 15 nm away ## 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 20050626034239A](https://openairdocs.org/incident/20050626034239A), Jun 26, 2005: Cessna 172M, Marysville, OH, Substantial damage. (-23) Aircraft was landing on runway 26. During the landing, aircraft drifted to the right. Pilot elected to add power. While attempting to take off, aircraft… 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.