The U.S. aircraft register, updated daily
Accidents · NTSB WPR14CA064 · Final report

Piper PA 16 accident near San Carlos, California, December 8, 2013

On December 8, 2013 at about 9:31 pm local time, a 1949 Piper PA 16, registered N6913, was substantially damaged in an accident during landing (landing roll) near San Carlos, California (San Carlos Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's failure to maintain directional control during the landing roll.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
December 8, 2013 · about 9:31 pm local time
Place
San Carlos, California · San Carlos Airport · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Piper PA 16 NO SERIES, built 1949 · all PA 16s on the register
Registration
N6913 · registry record · serial 16-642
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The pilot reported that the landing, in a tailwheel equipped airplane, was uneventful. During the landing roll, he lost control of the airplane which ground looped to the right. The left wing and elevator impacted the ground and both sustained substantial damage. The pilot reported no mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Loss of control on ground during landing (landing roll) defining event

The NTSB's findings

  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 213 hours in all; 169 in this make and model; 21 in the last 90 days; 13 in the last 30 days; 131 as pilot in command; 0 on instruments
  • Last flight review: January 13, 2012
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 2,727 hours
  • Last inspection: annual inspection, June 24, 2013; 47 hours since
  • Maximum gross weight: 1,650 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O235 (piston); 1,387 hours total

The flight

  • Departed from: LVK Livermore CA at 9:00 pm
  • Destination: SQL San Carlos CA
  • Flight plan: none
  • Runway 12, 2,600 ft by 75 ft

Weather at the time

  • Light: daylight
  • Wind: from 020° at 6 knots
  • Visibility: 10 statute miles
  • Sky: a few clouds at 15,000 ft
  • Temperature: 43°F (6°C), dew point 25°F (-4°C)
  • Altimeter: 30.25 inHg
  • Observation at 9:47 pm from SQL

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

1 document, released by the NTSB on April 22, 2014. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.