Accident Piper J3C-65 N30616,
ASN logo
ASN Wikibase Occurrence # 386122
 
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Saturday 17 March 2001
Time:16:27 LT
Type:Silhouette image of generic J3 model; specific model in this crash may look slightly different    
Piper J3C-65
Owner/operator:
Registration: N30616
MSN: 4983
Year of manufacture:1940
Total airframe hrs:3145 hours
Engine model:Continental C85-12
Fatalities:Fatalities: 0 / Occupants: 1
Aircraft damage: Substantial
Category:Accident
Location:Seattle, WA -   United States of America
Phase: Taxi
Nature:Private
Departure airport:Seattle-Boeing Field International Airport, WA (BFI/KBFI)
Destination airport:Seattle-Boeing Field International Airport, WA (BFI/KBFI)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
The pilot reported that he listened to the airport's Automatic Terminal Information Service (ATIS) prior to landing. After landing and turning onto a parallel taxiway, the aircraft ran over a 10-foot-long horizontal barricade, which was "sitting in [the] taxiway" approximately perpendicular to the taxiway centerline. The pilot, who was seated in the rear seat of the tailwheel-equipped aircraft (as required for solo flight for the type) at the time, reported that he was doing "S" turns for taxi visibility, but that the barricade was obstructed from view by the nose of the aircraft. Upon striking the barricade, the aircraft's left main gear collapsed and the left wing dropped, striking another barricade. The pilot stated that the presence and location of the barricade were not announced on ATIS. On-site investigation disclosed that the barricade extended to within two to three feet of the yellow taxiway centerline. Review of a re-recording of ATIS disclosed that ATIS announced closure of several taxiways, but did not indicate that barricades were in place on the parallel taxiway.

Probable Cause: The pilot's failure to visually detect the barricade, resulting in a collision with the barricade. Factors included the barricade, and inadequate information on the ATIS broadcast.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: SEA01LA065
Status: Investigation completed
Duration: 7 months
Download report: Final report

Sources:

NTSB SEA01LA065

Location

Revision history:

Date/timeContributorUpdates
05-Apr-2024 11:25 ASN Update Bot Added

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org