# NTSB ERA11LA105: Cessna 172, N4383Q, Dublin, NC, December 31, 2010 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: December 31, 2010, 16:30 local (21:30 UTC) - Place: Dublin, NC - Coordinates: 34.601665, -78.579444 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=34.6017&lon=-78.5794&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report August 22, 2011 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 78090 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA11LA105 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/78090/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=78090 - Page: https://openairdocs.org/ntsb/ERA11LA105 ## Probable cause The pilot’s improper touchdown speed which resulted in a runway overrun. Contributing to the accident was the undetermined malfunction of the airspeed indicator. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Indicating/recording systems: indep instrument (clock, etc)](https://openairdocs.org/ntsb-findings/01023120): Aircraft › Aircraft systems · Not specified (probable cause); cases with it: [Cessna 172L, 1 case](https://openairdocs.org/ntsb-findings/01023120/cases.md?model=2072432), [All aircraft, 6 cases](https://openairdocs.org/ntsb-findings/01023120/cases.md) - [Action: incorrect action performance](https://openairdocs.org/ntsb-findings/02041015): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Cessna 172L, 3 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md?model=2072432), [All aircraft, 1,386 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md) - [Performance/control parameters: airspeed](https://openairdocs.org/ntsb-findings/01062010): Aircraft › Aircraft oper/perf/capability · Malfunction (probable cause); cases with it: [Cessna 172L, 5 cases](https://openairdocs.org/ntsb-findings/01062010/cases.md?model=2072432), [All aircraft, 1,681 cases](https://openairdocs.org/ntsb-findings/01062010/cases.md) - [Performance/control parameters: airspeed](https://openairdocs.org/ntsb-findings/01062010): Aircraft › Aircraft oper/perf/capability · Capability exceeded (probable cause); cases with it: [Cessna 172L, 5 cases](https://openairdocs.org/ntsb-findings/01062010/cases.md?model=2072432), [All aircraft, 1,681 cases](https://openairdocs.org/ntsb-findings/01062010/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach-VFR pattern base: Flight instrument malf/fail](https://openairdocs.org/ntsb-events/334); cases with it: [Cessna 172L, 1 case](https://openairdocs.org/ntsb-events/334/sequence.md?model=2072432), [All aircraft, 56 cases](https://openairdocs.org/ntsb-events/334/sequence.md) - [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300) (defining event); cases with it: [Cessna 172L, 11 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=2072432), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) - [Landing-landing roll: Nose over/nose down](https://openairdocs.org/ntsb-events/096); cases with it: [Cessna 172L, 8 cases](https://openairdocs.org/ntsb-events/096/sequence.md?model=2072432), [All aircraft, 2,287 cases](https://openairdocs.org/ntsb-events/096/sequence.md) ## Analysis The pilot was repositioning the airplane to an unfamiliar airport equipped with a 2,186-foot-long turf runway. After arrival, he circled the airport several times, and initiated an approach to the runway. On final approach, the pilot performed a go-around due to glare from the sun, and elected to land on the opposite runway. While on the base-to-final turn, he noticed the airspeed indicator was reading zero, but reported feeling comfortable and elected to continue the approach. After touchdown on the wet turf runway about 1/3 down its length, he noticed the airplane was faster than he expected. The pilot applied the brakes, but was unable to stop the airplane. The airplane overran the runway, crossed a road, and nosed over in a field, where it came to rest inverted. Testing of the pitot-static system revealed no evidence of preimpact failure or malfunction. No determination could be made as to the reason for the airspeed indicator malfunction, as reported by the pilot. ## Factual narrative On December 31, 2010, about 1630 eastern standard time, a Cessna 172L, N4383Q, was substantially damaged during a runway overrun after landing at Dublin Field Airport (NC82), Dublin, North Carolina. The certificated private pilot, the sole occupant, was not injured. Visual meteorological conditions prevailed, and no flight plan was filed for the flight, which departed Curtis L. Brown Jr. Field Airport (EYF), Elizabethtown, North Carolina, about 1530. The personal flight was operated under the provisions of Title 14 Code of Federal Regulations Part 91. The pilot stated that the owner of the airplane asked him to fly the airplane from EYF to NC82 following the completion of its annual inspection. The pilot fueled the airplane, conducted a preflight inspection, and performed three touch-and-go landings at EYF before departing for NC82, which he had never flown to previously. According to the pilot, after arrival at NC82, he circled the airstrip several times to familiarize himself, then initiated a visual approach to runway 21 but performed a go-around due to glare from the sun. Because the wind was calm, he elected to land on runway 03, and reported the approach for landing was "typical" until the base-to-final turn, where he noticed the airspeed indicator was indicating zero. He tapped on the glass of the instrument but there was no change. He felt "reasonably comfortable" and elected to continue the approach, touching down about one-third down the wet 2,186-foot turf runway. He noted that the airplane was faster than he had expected, and he applied the brakes to stop the airplane, but was unable. The airplane overran the end of the runway, crossed a road, and travelled into a field where the airplane nosed over and came to rest inverted. The pilot stated that he received no anomalous indications from any of the flight instruments prior to turning onto final approach. Post accident examination of the airplane by a Federal Aviation Administration (FAA) inspector revealed substantial damage to the right wing spar, and vertical stabilizer. The airspeed indicator displayed 145 miles per hour (mph) as depicted by the outer scale, or approximately 126 knots as depicted by the inner scale. The altimeter displayed the correct field elevation, and the vertical speed indicator displayed zero. The inspector stated that, when the pitot tube was blown into, the airspeed indicator "pegged out," then returned to the original value after the air pressure was removed. The airplane was recovered for further examination which required removal in part of the left wing. The airplane's pitot-static system was tested with FAA oversight following recovery of the airplane. Before the start of the test the airspeed indicator read 0 mph. A calibration test box was plumbed to the fuselage pitot line at the fuselage sidewall, and air pressure was applied in 20 mph increments from 40 mph to red line; a calibration error of approximately 5 mph was noted. Air pressure wasreduced to 140 mph and maintained for approximately 5 minutes; the airspeed indicator maintained a steady indication throughout the test. Air pressure was then reduced to zero and the airspeed indication decreased accordingly with no sticking noted. The entire test was repeated with the same results noted. Testing of the section of pitot tube in the left wing revealed no leaks. A test line was connected to the end of pitot-static line at the left wing root and also to the end of pitot-static line at the fuselage root. Testing of the entire pitot-static system was performed in that configuration and no calibration error or sticking was noted of the airspeed indicator. The pilot held a private pilot certificate with airplane single engine land and instrument airplane ratings. He reported approximately 500 total hours of flight experience, of which approximately 50 hours were in the accident airplane make and model. His most recent third-class FAA medical certificate was issued February 12, 2008. According to FAA records, the airplane was manufactured in 1971, and had accumulated a total operating time of 3894.2 hours. The airplane's last annual inspection was completed December 30, 2010. According to the owner of the airplane, the pitot-static system had not been tested in several years, since the airplane was operated only under visual flight rules. The 1640 weather observation at EYF, located approximately 7 nautical miles southeast of the accident site, included calm winds, 10 miles visibility, clear skies, temperature 16 degrees C, dew point 7 degrees C, and an altimeter setting of 30.24 inches of mercury. The pilot was advised to complete and submit the NTSB Pilot/Operator Aircraft Accident/Incident Report Form; however, the report was not received by NTSB. ## Aircraft - Registration: [N4383Q](https://openairdocs.org/aircraft/N4383Q), registered now, S/N 17260283, built 1971 (OpenAirDocs) - Reported make and model: CESSNA 172 (L) - Registry model: [Cessna 172L](https://openairdocs.org/model/cessna-172l) (registry code 2072432) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17260283 - Airframe hours: 3894 - Engines: LYCOMING O320 160 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Bladen Aviation Inc - Registered owner: Bladen Aviation Inc - Airworthiness certificate: Standard, Normal - Last inspection: Annual, December 30, 2010 - Departed: EYF, Elizabethtown, NC - Destination: NC82, Dublin, NC - Airport: NC82, Dublin Field, runway 03, 2,186 × 66 ft, grass/turf ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 39; injuries: none; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, with waivers/limitations; seat: left; flight hours: 500 total, 50 in this make and model ## Weather - Conditions: Visual (VMC), Day - Wind: calm - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 61 °F, dew point 45 °F - Altimeter: 30.23 inHg - Observed at: EYF, 7 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 20101231054809A](https://openairdocs.org/incident/20101231054809A), Dec 31, 2010: Cessna 172L, Dublin, NC, Substantial damage. [privacy data omitted] Stated that the airspeed indicator on the aircraft became inoperative on the base leg to NC-82 airport. [privacy data omitted] Reported… ## Other investigations on N4383Q (2) 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 ATL95LA063](https://openairdocs.org/ntsb/ATL95LA063), Mar 10, 1995: Cessna 172L (N4383Q), Smyrna, TN, no damage. Probable cause: THE FLIGHT INSTRUCTOR'S FAILURE TO ENSURE THAT THE MAGNETOS WERE NOT ENERGIZED PRIOR TO POSITIONING THE PROPELLER, AND THE DUAL STUDENT'S FAILURE TO PLACE THE IGNITION SWITCH IN THE OFF POSITION… - [NTSB CHI76FEE22](https://openairdocs.org/ntsb/CHI76FEE22), Oct 14, 1975: Cessna 172L (N4383Q), Rockfort, IL, substantial damage ## Docket (5 files) The files NTSB released with the investigation on June 23, 2011, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=78090. 1.8 MB in all. - Weather Reports and Records (item 1, .PDF, 126 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40348081&FileExtension=.PDF&FileName=Weather%20Reports%20and%20Records-Master.PDF - Record of NTSB Conversation (item 2, .PDF, 96 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40344919&FileExtension=.PDF&FileName=Record%20of%20NTSB%20Conversation-Master.PDF - FAA Inspector Statements (item 3, .PDF, 107 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40348078&FileExtension=.PDF&FileName=FAA%20Inspector%20Statements-Redacted.PDF - Photos (Courtesy FAA) (item 4, .PDF, 4 photos, 1.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40345028&FileExtension=.PDF&FileName=Photos%20(Courtesy%20FAA)-Master.PDF - Memorandum for Record - Airplane Owner (item 5, .PDF, 85 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40348105&FileExtension=.PDF&FileName=Memorandum%20for%20Record%20-%20Airplane%20Owner-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.