# NTSB ERA14CA039: Taylorcraft BC 65, N52CW, Fallston, MD, November 4, 2013 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: November 4, 2013, 10:00 local (15:00 UTC) - Place: Fallston, MD - Coordinates: 39.520542, -76.420486 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=39.5205&lon=-76.4205&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-landing roll: Loss of control on ground](https://openairdocs.org/ntsb-events/230) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report April 1, 2014 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - NTSB case key (mKey): 88404 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA14CA039 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/88404/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=88404 - Page: https://openairdocs.org/ntsb/ERA14CA039 ## Probable cause The pilot's failure to maintain directional control during landing resulting in collision with equipment off the side of the runway. Contributing to the accident was the pilot's intentional landing on a closed runway with a tailwind. ## 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: [All aircraft, 3,969 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: [All aircraft, 9,308 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Airport facilities/design: runway/landing area condition](https://openairdocs.org/ntsb-findings/03017035): Environmental issues › Operating environment · Decision related to condition (probable cause); cases with it: [All aircraft, 61 cases](https://openairdocs.org/ntsb-findings/03017035/cases.md) - [Wind: tailwind](https://openairdocs.org/ntsb-findings/03034015): Environmental issues › Conditions/weather/phenomena · Decision related to condition (probable cause); cases with it: [All aircraft, 594 cases](https://openairdocs.org/ntsb-findings/03034015/cases.md) - [Object/animal/substance: ground equipment](https://openairdocs.org/ntsb-findings/03022050): Environmental issues › Physical environment · Contributed to outcome; cases with it: [All aircraft, 52 cases](https://openairdocs.org/ntsb-findings/03022050/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-landing roll: Loss of control on ground](https://openairdocs.org/ntsb-events/230) (defining event); cases with it: [All aircraft, 4,590 cases](https://openairdocs.org/ntsb-events/230/sequence.md) - [Landing-landing roll: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [All aircraft, 10,154 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The pilot instructed the runway repair technicians to move their equipment so that he could depart from the closed runway that was NOTAM'd as such by the airport operator. The pilot/owner then took off downwind. Later, the pilot returned in the accident airplane and the technicians were surprised when the airplane "committed" to landing downwind on the closed runway. The technicians quickly moved their equipment from the runway surface but the pilot was unable to stop the airplane before striking the left wing against a construction vehicle off the left side of the runway, which resulted in substantial damage. In interviews with Federal Aviation Administration inspectors, the pilot did not report any mechanical deficiencies with his airplane that would preclude normal operation. According to NTSB records, this was the pilot's fourth accident in the previous 3 years. ## Factual narrative The pilot instructed the runway repair technicians to move their equipment so that he could depart from the closed runway that was NOTAM'd as such by the airport operator. The pilot/owner then took off downwind. Later, the pilot returned in the accident airplane and the technicians were surprised when the airplane "committed" to landing downwind on the closed runway. The technicians quickly moved their equipment from the runway surface but the pilot was unable to stop the airplane before striking the left wing against a construction vehicle off the left side of the runway, which resulted in substantial damage. In interviews with Federal Aviation Administration inspectors, the pilot did not report any mechanical deficiencies with his airplane that would preclude normal operation. According to NTSB records, this was the pilot's fourth accident in the previous 3 years. ## Aircraft - Registration: N52CW (not matched to a registry record) - Reported make and model: TAYLORCRAFT BC 65 (65) - Category: Airplane - Serial number: 1716 - Year built: 1946 - Engines: CONT MOTOR C85 SERIES 85 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Walker J C - Registered owner: Walker J C - Airworthiness certificate: Standard, Normal - Last inspection: Annual, April 6, 2013 - Departed: 0W3, CHURCHVILLE, MD - Destination: W42, Fallston, MD - Airport: W42, Fallston, runway 22, 2,200 × 50 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 78; injuries: none; commercial; airplane ratings: multi-engine land, single-engine sea, single-engine land; medical: class 2, with waivers/limitations; seat: left; flight hours: 8,793 total, 40 in this make and model ## Weather - Conditions: Visual (VMC), Day - Wind: 20° at 5 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 39 °F, dew point 21 °F - Altimeter: 30.63 inHg - Observed at: KMTN, 11 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 20131104020699A](https://openairdocs.org/incident/20131104020699A), Nov 4, 2013: Taylorcraft BC-65, Fallston, MD, Substantial damage. Pilot departed W42 at approximately 0830HRS with his Luscombe aircraft and landed at 0W3 at approximately 0900HRS for the purpose of a maintenance relocation… ## Docket (6 files) The files NTSB released with the investigation on March 14, 2014, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=88404. 486 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 Memorandum for Record (item 1, .PDF, 52 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40408289&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1%20Memorandum%20for%20Record-Master.PDF - FAA Inspectors Statements (item 2, .PDF, 72 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40408290&FileExtension=.PDF&FileName=FAA%20Inspectors%20Statements-Master.PDF - Annual Inspection Receipt (item 3, .PDF, 55 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40408291&FileExtension=.PDF&FileName=Annual%20Inspection%20Receipt-Redacted.PDF - Photo 1 - View of Damage to Leading Edge of Left Wing (item 4, .PDF, 148 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40408293&FileExtension=.PDF&FileName=Photo%201%20-%20View%20of%20Damage%20to%20Leading%20Edge%20of%20Left%20Wing-Master.PDF - Photo 2 - View of Left Wing Damage facing Cabin (item 5, .PDF, 92 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40408294&FileExtension=.PDF&FileName=Photo%202%20-%20View%20of%20Left%20Wing%20Damage%20facing%20Cabin-Master.PDF - Photo 3 - Trailing Edge View of Wing Damage at Cabin (item 6, .PDF, 67 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40408296&FileExtension=.PDF&FileName=Photo%203%20-%20Trailing%20Edge%20View%20of%20Wing%20Damage%20at%20Cabin-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.