FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA17CA564 · Boeing PT 13 D

28 Sept 2017 · Skagit, WA, United States

Boeing PT 13 D · Accident: ground collision during landing

From Mears Field Airport (3W5) to Skagit Regional Airport (KBVS)

Report a problem

Event

NTSB case
GAA17CA564
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Boeing PT 13 D

Aircraft type
Boeing PT-13
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N43JM
Operator
Unknown
Onboard fatalities
Unknown
Route
From Mears Field Airport (3W5), Concrete, WATo Skagit Regional Airport (KBVS), Burlington, WA
Aircraft age
About 74 years (built 1943)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing · landing roll
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Ground collision
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Environmental issues › Physical environment
  • Personnel issues › Psychological

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

According to the pilot in the high-performance, tailwheel-equipped biplane, he landed on a turf airstrip which he described as "long and wide." He added that "there was no wind." During the landing roll, he taxied the biplane along the right edge of the runway, and the lower right wing struck a precision approach path indicator (PAPI) control box. The pilot reported that the accident was caused by a lack of situational awareness during the landing roll.

The PAPI lights were identified in the airport facility directory.

The biplane sustained substantial damage to the lower right-wing spar.

The pilot reported that there were no preaccident mechanical malfunctions or failures with the biplane that would have precluded normal operation.

Probable cause

The pilot’s failure to maintain clearance from airport lighting during the landing roll.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA17CA564
Event ID
20170928X72326
Case number
GAA17CA564
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: d4bb431b9a80dba94313604323dac525c04602380f8a5702810da252864c0508; retrieved 2026-09-16T05:53:56.443Z.