# NTSB ERA09CA207: Piper PA28-151, N41568, Dover, DE, March 20, 2009 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: March 20, 2009, 14:40 local (18:40 UTC) - Place: Dover, DE - Coordinates: 39.217777, -75.59111 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=39.2178&lon=-75.5911&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing: Loss of control in flight](https://openairdocs.org/ntsb-events/240) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report June 11, 2009 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - NTSB case key (mKey): 73533 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA09CA207 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/73533/pdf - Page: https://openairdocs.org/ntsb/ERA09CA207 ## Probable cause The pilot's failure to maintain directional control during landing. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: directional control](https://openairdocs.org/ntsb-findings/01062020): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Piper PA-28-151, 9 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=7102805), [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Piper PA-28-151, 10 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=7102805), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Wind: gusts](https://openairdocs.org/ntsb-findings/03034045): Environmental issues › Conditions/weather/phenomena · Ability to respond/compensate (probable cause); cases with it: [Piper PA-28-151, 2 cases](https://openairdocs.org/ntsb-findings/03034045/cases.md?model=7102805), [All aircraft, 1,199 cases](https://openairdocs.org/ntsb-findings/03034045/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing: Loss of control in flight](https://openairdocs.org/ntsb-events/240) (defining event); cases with it: [Piper PA-28-151, 9 cases](https://openairdocs.org/ntsb-events/240/sequence.md?model=7102805), [All aircraft, 5,002 cases](https://openairdocs.org/ntsb-events/240/sequence.md) - [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Piper PA-28-151, 12 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=7102805), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) - [Landing-landing roll: Ground collision](https://openairdocs.org/ntsb-events/200); cases with it: [Piper PA-28-151, 4 cases](https://openairdocs.org/ntsb-events/200/sequence.md?model=7102805), [All aircraft, 618 cases](https://openairdocs.org/ntsb-events/200/sequence.md) ## Analysis The pilot conducted one landing on runway 27, but he "did not like it" because it was "gusty," so he opted to conduct a second landing. The pilot stated that as the airplane was "nearing touchdown," it unexpectedly began a turn to the left. The airplane first touched down approximately 75 feet left of the edge of the runway. It continued on a southerly arc away from the runway, passed through an aircraft tie-down area, and struck two parked airplanes. The accident airplane's right wing separated from the fuselage at the wing root, and the airplane came to rest approximately 346 feet from the centerline of the runway. Runway 27 was 3,582 feet long and 60 feet wide, with a displaced threshold of 350 feet. The only wind information available at the accident airport was a wind sock. About the time of the accident, winds at an airport 9 miles southeast of the airport were reported to be from 330 degrees at 12 knots, with gusts to 18 knots. Calculations revealed that if these winds were present at the accident airport, they would have resulted in crosswind components from 11.7 to 17.5 knots. A required cockpit placard in the airplane stated that the "demonstrated crosswind component" was 17 knots. The pilot reported that he obtained his weather information from commercial television and radio stations. He did not report experiencing any mechanical failures or malfunctions with the airplane during the accident landing. ## Factual narrative "THIS CASE WAS MODIFIED MAY 5, 2009." The pilot conducted one landing on runway 27, but he "did not like it" because it was "gusty," so he opted to conduct a second landing. The pilot stated that as the airplane was "nearing touchdown," it unexpectedly began a turn to the left. The airplane first touched down approximately 75 feet left of the edge of the runway. It continued on a southerly arc away from the runway, passed through an aircraft tie-down area, and struck two parked airplanes. The accident airplane's right wing separated from the fuselage at the wing root, and the airplane came to rest approximately 346 feet from the centerline of the runway. Runway 27 was 3,582 feet long, 60 feet wide, with a displaced threshold of 350 feet. The only wind information available at the accident airport was a wind sock. About the time of the accident, winds at an airport 9 miles southeast of the airport were reported to be from 330 degrees at 12 knots, with gusts to 18 knots. Calculations revealed that if these winds were present at the accident airport, they would have resulted in crosswind components from 11.7 to 17.5 knots. A required cockpit placard in the airplane stated that the "demonstrated crosswind component" was 17 knots. The pilot reported that he obtained his weather information from commercial television and radio stations. He did not report experiencing any mechanical failures or malfunctions with the airplane during the accident landing. ## Aircraft - Registration: [N41568](https://openairdocs.org/deregistered/N41568-2015-04-30), registration cancelled 2015-04-30, S/N 28-7415274, built 1974 (OpenAirDocs) - Reported make and model: PIPER PA28-151 - Registry model: [Piper PA-28-151](https://openairdocs.org/model/piper-pa-28-151) (registry code 7102805) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 28-7415274 - Airframe hours: 3557 - Engines: LYCOMING O-320 SERIES 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Phill-Air Inc - Registered owner: Phill-Air Inc - Airworthiness certificate: Standard, Normal; Standard, Utility - Last inspection: 100 hour, October 12, 2008 - Departed: 33N, Dover, DE - Destination: 33N, Dover, DE - Airport: 33N, Delaware Airpark, runway 27, 3,582 × 60 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 59; injuries: none; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; last flight review May 8, 2007; seat: left; flight hours: 181 total, 39 in this make and model, 147 as pilot in command ## Weather - Conditions: Visual (VMC), Day - Wind: 330° at 12 knots, gusting 18 - Visibility: 10 statute miles - Lowest ceiling: 5,500 ft overcast - Temperature: 45 °F, dew point 27 °F - Observed at: DOV, 9 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 20090320004219A](https://openairdocs.org/incident/20090320004219A), Mar 20, 2009: Piper PA28151, Dover/Cheswold, DE, Substantial damage. (-23) Pilot stated that he departed summit airport (kevy), middletown, DE, without a weather report and was practicing landings at K33N. He had made one… 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.