# NTSB NYC96LA136: Cessna 172N, N4776E, Newry, PA, June 28, 1996 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: June 28, 1996, 11:50 local (15:50 UTC) - Place: Newry, PA - Coordinates: 40.390884, -78.430557 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=40.3909&lon=-78.4306&mi=10 - Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report February 1, 1997 - Report: Approved by Office Director - NTSB case key (mKey): 39204 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=NYC96LA136 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/39204/pdf - Page: https://openairdocs.org/ntsb/NYC96LA136 ## Probable cause failure of the pilot to identify the inoperative airspeed indication and abort the takeoff, while there was sufficient runway remaining; excessive speed during the approach/landing; and the pilot's failure to perform a go-around after not attaining a proper touchdown point during the landing. A factor relating to the accident was: the blocked pitot tube, which resulted in an inoperative airspeed indicator. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Airframe/component/system failure/malfunction, takeoff - roll/run - pitot/static system - blocked(total) (contributing factor) - flight/nav instruments,airspeed indicator - inoperative - aborted takeoff - not performed, pilot in command (cause) - Overrun, landing - roll - airspeed - excessive (cause) - proper touchdown point - not attained - go-around - not performed, pilot in command (cause) - On ground/water encounter with terrain/water, landing - roll - terrain condition - rough/uneven ## Analysis During the takeoff roll, the pilot observed that the airspeed indicator was inoperative. However, he said that by the time he realized the problem, the airplane was too far down the runway to abort the takeoff. He continued the takeoff and flew about 1.2 hours before returning to landing. The airplane was high and fast during the first approach to land, and the pilot decided to go-around. After the second approach, the airplane touched down about half way down the 3,415 foot long runway. The pilot stated that he applied full brakes; however, the airplane was too fast and continued off the departure end of the runway. Subsequently, it encountered rough terrain and was damaged. Examination of the airplane revealed that the pitot tube was blocked with a sediment. ## Factual narrative On June 28, 1996, about 1150 eastern daylight time, a Cessna 172N, N4776E, was substantially damaged when it overran the runway during the landing at the Blue Knob Valley Airport, Newry, Pennsylvania. The private pilot and passenger were not injured. Visual meteorological conditions prevailed for the local flight. No flight plan was filed for the personal flight conducted under 14 CFR Part 91. The pilot stated, in the NTSB form 6120.1/2: "My son and I arrived at the airport and I preflighted the airplane. We taxied to the run-up area for runway 29. I "ran-up" the engine, checked the gauges and set the flight instruments and radio. We cleared for take off and during the take-off roll, I noticed the airspeed was not working properly. It bounced a few times and then quit. By this time I was too far down the runway to abort the takeoff. I took off and we flew locally for 1.2 hours. We flew back to the airport to land. I was concerned about coming in too slow and stalling out. I use 10 [degrees] flaps for a final but was too high and fast to touch down. I made a go around and used 20 [degrees] flaps for final. I touched down about 1/3 to 1/2 down the runway, applied full brakes but was still going too fast and ran off the end of the runway." Examination of the wreckage by a Federal Aviation Administration Inspector revealed sediment clogged the pitot tube. According to the Airport Facility Directory, runway 29 was a 3,415 foot long, 92 foot wide, dirt runway with no obstructions. The weather at a nearby airport was reported as ceiling 3,500 broken; visibility 12 miles; temperature 80 degrees F; dewpoint 60 degrees F; altimeter 30.20" Hg; wind from 330 degrees at 7 knots. According to the Cessna 172 Pilot Operating Handbook, for the above conditions, the takeoff and landing distances were approximately 1,300 and 900 feet respectively. ## Aircraft - Registration: [N4776E](https://openairdocs.org/aircraft/N4776E), registered now, S/N 17271641, built 1978 (OpenAirDocs) - Reported make and model: Cessna 172N - Registry model: [Cessna 172N](https://openairdocs.org/model/cessna-172n) (registry code 2072434) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17271641 - Engines: Lycoming O-320-H2AD 160 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Vernon D'Arley Mock - Registered owner: Blue Knob Valley Airport Inc - Airworthiness certificate: Standard, Normal - Departed: 7G4 - Airport: 7G4, Blue Knob Valley, runway 29, 3,415 × 92 ft, dirt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 72; private; airplane ratings: single-engine land; medical: class 3, valid medical--w/ waivers/lim; seat: left; flight hours: 225 total, 11 in this make and model, 225 as pilot in command ## Weather - Conditions: Visual (VMC), Day - Wind: 330° at 7 knots - Visibility: 12 statute miles - Lowest ceiling: 3,500 ft broken - Temperature: 81 °F, dew point 61 °F - Altimeter: 30.00 inHg - Observed at: JST, 18 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 19960628015549A](https://openairdocs.org/incident/19960628015549A), Jun 28, 1996: Cessna 172N, Newry, PA, Substantial damage. Aircraft landed on runway with inoperative aispeed indicator, approach too fast, ran off end of runway, hit ditch. ## Other investigations on N4776E (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 GAA16CA096](https://openairdocs.org/ntsb/GAA16CA096), Dec 26, 2015: Cessna 172 (N4776E), Punta Gorda, FL, substantial damage. Probable cause: The student pilot's failure to maintain obstacle clearance while taxiing on the ramp, resulting in a collision with an object. - [NTSB CHI00LA021](https://openairdocs.org/ntsb/CHI00LA021), Oct 25, 1999: Cessna 172N (N4776E), Crandon, WI, substantial damage. Probable cause: the deer that ran out onto the runway and collided with the airplane. A factor associated with the accident was the night lighting 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.