# Incident 20051120028569I: Piper J3C65, Vacaville, CA, November 20, 2005

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: November 20, 2005
- Place: Vacaville, CA
- Airport: Nut Tree Airport
- Phase of flight: Roll-Out (Fixed Wing)
- Operating rules: General operating rules (Part 91)
- Location: 38.3782° N, 121.9612° W: Placed by OpenAirDocs at NUT TREE (VCB), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=38.3782&lon=-121.9612&mi=10
- Aircraft: N30669, registered now (https://openairdocs.org/aircraft/N30669) (OpenAirDocs)
- Registry model: Piper J3C-65 (registry code 7100510, https://openairdocs.org/model/piper-j3c-65) (OpenAirDocs)
- Registry engine: Continental A&C75 series (registry code 17005, https://openairdocs.org/engine/continental-a-c75-series) (OpenAirDocs)
- Reported make and model: PIPER J3C65
- People aboard: 1
- Fatal injuries: 0
- Pilot certificates: Student
- Pilot flight hours: 180 total, 120 in this make and model, 30 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20051120028569I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) WHILE DOING THREE POINT TOUCH AND GO LANDING ON RUNWAY 02 AT VACAVILLE CA, NUT TREE AIRPORT (VCB) ON NOVEMBER 20, 2005 DURING VMC CONDITIONS WITH LIGHT AND VARIABLE WINDS THE PIPER J3 CUB SUFFERED MINOR DAMAGE. THE PILOT STATED THAT DURING ROLL-OUT FROM A NORMAL LANDING, JUST PRIOR TO APPLYING POWER AT A SPEED OF ABOUT 10 TO 20 MPH THE AIRCRAFT SUDDENLY VEERED TO THE LEFT. THE AIRCRAFT WAS HEADING OFF THE RUNWAY INTO A DIRT FIELD. THE PILOT BEGAN TO APPLY POWER TO REGAIN CONTROL BUT THE AIRCRAFT MAIN LANDING HIT A DIRT BERM AND STOPPED. THE STUDENT PILOT AND LONE OCCUPANT WAS NOT INJURED. THE DAMAGE WAS CONFINED TO THE LEFT HAND MAIN LANDING GEAR LEG, AND THE BUNGE ASSEMBLY'S TUBULAR SUPPORT STRUT. DURING EXAMINATION OF THE AIRCRAFT THERE WAS NO MECHANICAL FAULT FOUND TO EXPLAIN WHY THE AIRCRAFT VEERED TO THE LEFT AND DEPARTED THE RUNWAY.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft 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. For accidents, the NTSB's own investigation is the fuller record.

---
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.