20160429004149I

Incident · No damage

FAA incident report · Piper PA-28R-200 · San Carlos, CA · April 29, 2016

Date: April 29, 2016 · 15:00 local
Place: San Carlos, CA
Phase of flight: Cruise/Level Flight
Operating rules: General operating rules (Part 91)
Damage: No damage
Aircraft: N200KR
NTSB investigation: NTSBWPR16IA100
Reported as: Piper PA-28R-200
Reported engine: Lycoming O&VO-360 series
People aboard: 1
Fatal injuries: 0
Other injuries: 0

N200KRRegistered now · Piper PA-28R-200S/N 28R-7635176 · Built 1976 Airframe modelPiper PA-28R-200 Engine modelLycoming O&VO-360 seriesReciprocating

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry by N-number and event date, checked against the reported make and model; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

San Carlos, CA (sql): BYF17, N200KR, PA28, aircraft departed San Carlos from rwy 30 for a local area flight. At 3 miles north of the airport the pilot indicated their intentions to return to the airport for landing due to an equipment issue. When queried by the tower controller as to the type of problem, the pilot responded with a broken throttle cable issue, that they would be fast on final and kill the engine upon touchdown and roll off the runway at the first available intersection. Airport operations standby alert vehicle was informed and standing by. Aircraft landed without incident, shut down the engine and exited the runway at intersection charlie. Aircraft came to a stop on kilo taxiway clear of the runway. Airport operations assisted aircraft off of the movement area to parking notf'd sjc fsdo/mike; San Carlos flight ctr/mor POB: unkn, injuries: none, damage: none rptd, 4/29 2200Z

As the FAA filed it

SAN CARLOS, CA (SQL): BYF17, N200KR, PA28, AIRCRAFT DEPARTED SAN CARLOS FROM RWY 30 FOR A LOCAL AREA FLIGHT. AT 3 MILES NORTH OF THE AIRPORT THE PILOT INDICATED THEIR INTENTIONS TO RETURN TO THE AIRPORT FOR LANDING DUE TO AN EQUIPMENT ISSUE. WHEN QUERIED BY THE TOWER CONTROLLER AS TO THE TYPE OF PROBLEM, THE PILOT RESPONDED WITH A BROKEN THROTTLE CABLE ISSUE, THAT THEY WOULD BE FAST ON FINAL AND KILL THE ENGINE UPON TOUCHDOWN AND ROLL OFF THE RUNWAY AT THE FIRST AVAILABLE INTERSECTION. AIRPORT OPERATIONS STANDBY ALERT VEHICLE WAS INFORMED AND STANDING BY. AIRCRAFT LANDED WITHOUT INCIDENT, SHUT DOWN THE ENGINE AND EXITED THE RUNWAY AT INTERSECTION CHARLIE. AIRCRAFT CAME TO A STOP ON KILO TAXIWAY CLEAR OF THE RUNWAY. AIRPORT OPERATIONS ASSISTED AIRCRAFT OFF OF THE MOVEMENT AREA TO PARKING NOTF'D SJC FSDO/MIKE; SAN CARLOS FLIGHT CTR/MOR POB: UNKN, INJURIES: NONE, DAMAGE: NONE RPTD, 4/29 2200Z

NTSB investigation

The NTSB’s investigation of this event, with its probable cause and findings. Matched to this report by N-number and date.

NTSB WPR16IA100Incident · No injuriesIncident investigationFinal reportSan Carlos, CAThe failure of maintenance personnel to properly install and secure the input swivel boot on the swivel joint, which resulted in excessive vibration that led to fatigue cracks and failure of the throttle cable.Apr 29, 2016 · No damage