# NTSB WPR14CA358: Boeing A75N1 (PT-17), Seattle, WA, August 16, 2014 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: August 16, 2014, 11:30 local (18:30 UTC) - Place: Seattle, WA - Coordinates: 47.5275, -122.300552 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=47.5275&lon=-122.3006&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Loss of control on ground](https://openairdocs.org/ntsb-events/230) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report November 13, 2014 - Report: Approved by Office Director - NTSB office: Western Pacific Region - NTSB case key (mKey): 89976 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR14CA358 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/89976/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=89976 - Page: https://openairdocs.org/ntsb/WPR14CA358 ## Probable cause The pilot's inadequate flare and failure to maintain aircraft control during landing. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: landing flare](https://openairdocs.org/ntsb-findings/01062041): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [All aircraft, 1,285 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md) - [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,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: [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-flare/touchdown: Loss of control on ground](https://openairdocs.org/ntsb-events/230) (defining event); cases with it: [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) - [Landing-flare/touchdown: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) - [Landing-flare/touchdown: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The pilot had an uneventful departure on his first solo flight to remain in the traffic pattern. Shortly after, the pilot reported that he was having problems with the radio and communications with the tower controller. The pilot decided to land with a full stop to have the radio repaired. On the first landing attempt the airplane bounced and the pilot initiated a go-around. On the second landing attempt, the airplane floated down the runway and suddenly lost lift and bounced again. The pilot aborted the landing and applied power. The airplane subsequently veered left into the grass field between the runways and nosed over after colliding with a berm which resulted in substantial damage to the wing. At the time of the accident, the pilot reported a light tailwind. The pilot further reported no preimpact mechanical failures or malfunctions with the airplane that would have precluded normal operation. ## Factual narrative The pilot had an uneventful departure on his first solo flight to remain in the traffic pattern. Shortly after, the pilot reported that he was having problems with the radio and communications with the tower controller. The pilot decided to land with a full stop to have the radio repaired. On the first landing attempt the airplane bounced and the pilot initiated a go-around. On the second landing attempt, the airplane floated down the runway and suddenly lost lift and bounced again. The pilot aborted the landing and applied power. The airplane subsequently veered left into the grass field between the runways and nosed over after colliding with a berm which resulted in substantial damage to the wing. At the time of the accident, the pilot reported a light tailwind. The pilot further reported no preimpact mechanical failures or malfunctions with the airplane that would have precluded normal operation. ## Aircraft - Registration: B719BL (not matched to a registry record) - Reported make and model: BOEING A75N1 (PT-17) - Category: Airplane - Serial number: 75-2246 - Year built: 1941 - Airframe hours: 37 - Engines: Jacobs R-755B2M 275 hp reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Robert William Lisowski - Registered owner: Robert William Lisowski - Airworthiness certificate: Standard, Aerobatic - Last inspection: 100 hour, July 2, 2014 - Departed: KBFI, Seattle, WA - Destination: KBFI, Seattle, WA - Airport: KBFI, Boeing Field, runway 13R, 10,000 × 200 ft, asphalt - Equipment: Electronic flight bag or handheld device, Handheld GPS ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 55; injuries: none; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; last flight review December 10, 2013; seat: rear; flight hours: 130 total, 47 in this make and model, 110 as pilot in command, 20 in the last 90 days, 20 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 310° at 3 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 66 °F, dew point 57 °F - Altimeter: 30.09 inHg - Observed at: KBFI ## Docket (3 files) The files NTSB released with the investigation on October 29, 2014, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=89976. 3.8 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 3.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40418308&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - FAA Damage Assessment Correspondence (item 2, .PDF, 638 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40418310&FileExtension=.PDF&FileName=FAA%20Damage%20Assessment%20Correspondence-Redacted.PDF - Photo 1 – View of Lower Right Wing (Photo Courtesy of FAA) (item 3, .PDF, 11 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40418311&FileExtension=.PDF&FileName=Photo%201%20%E2%80%93%20View%20of%20Lower%20Right%20Wing%20(Photo%20Courtesy%20of%20FAA)%0D%0A-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.