20080627840269I

Incident · Minor damage

FAA incident report · Piper J3C-65 · Robbinsville, NJ · June 27, 2008

Date
June 27, 2008 · 20:20 local
Place
Robbinsville, NJ
Airport
Trenton-Robbinsville
Phase of flight
Roll-Out (Fixed Wing)
Operating rules
General operating rules (Part 91)
Operator
VWGJ
Damage
Minor damage
Aircraft
N42183
Reported as
Piper J3C65
Reported engine
Lycoming O320B2B
People aboard
1
Fatal injuries
0
Pilot’s flight hours
1,092 total800 in this make and model50 in the last 90 days

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.

(-23) The first FAA notification of this incident was on 06/28/08 (approximately 23 hours after the event) when the pilot contacted the eastern region ops center by phone. At that time the pilot stated this was an unplanned landing because he was "running out of daylight". He said that on landing the aircraft veered off the runway and flipped over on its back. There are no witnesses to this incident and the pilot declined to give any details until he had conferred with legal counsel. The pilot's lawyer submitted a statement on 07/03/2008 which stated that after touchdown on runway 29, during roll-out, the aircraft began to veer to the left and the aircraft did not respond to rudder and brake corrections. "The aircraft rolled off the runway onto the grass and, although the stick was held fully back, the tail came up, the nose struck the ground and the aircraft turned over on its back." A check of rudder control continuity and brake system intergrity was accomplished on 07/11/2008. While there was damage to the rudder when the aircraft flipped, the inspector was able to verify the integrity of the rudder and brake systems. There were no recent write-ups for rudder or brake issues.

As the FAA filed it

(-23) THE FIRST FAA NOTIFICATION OF THIS INCIDENT WAS ON 06/28/08 (APPROXIMATELY 23 HOURS AFTER THE EVENT) WHEN THE PILOT CONTACTED THE EASTERN REGION OPS CENTER BY PHONE. AT THAT TIME THE PILOT STATED THIS WAS AN UNPLANNED LANDING BECAUSE HE WAS "RUNNING OUT OF DAYLIGHT". HE SAID THAT ON LANDING THE AIRCRAFT VEERED OFF THE RUNWAY AND FLIPPED OVER ON ITS BACK. THERE ARE NO WITNESSES TO THIS INCIDENT AND THE PILOT DECLINED TO GIVE ANY DETAILS UNTIL HE HAD CONFERRED WITH LEGAL COUNSEL. THE PILOT'S LAWYER SUBMITTED A STATEMENT ON 07/03/2008 WHICH STATED THAT AFTER TOUCHDOWN ON RUNWAY 29, DURING ROLL-OUT, THE AIRCRAFT BEGAN TO VEER TO THE LEFT AND THE AIRCRAFT DID NOT RESPOND TO RUDDER AND BRAKE CORRECTIONS. "THE AIRCRAFT ROLLED OFF THE RUNWAY ONTO THE GRASS AND, ALTHOUGH THE STICK WAS HELD FULLY BACK, THE TAIL CAME UP, THE NOSE STRUCK THE GROUND AND THE AIRCRAFT TURNED OVER ON ITS BACK." A CHECK OF RUDDER CONTROL CONTINUITY AND BRAKE SYSTEM INTERGRITY WAS ACCOMPLISHED ON 07/11/2008. WHILE THERE WAS DAMAGE TO THE RUDDER WHEN THE AIRCRAFT FLIPPED, THE INSPECTOR WAS ABLE TO VERIFY THE INTEGRITY OF THE RUDDER AND BRAKE SYSTEMS. THERE WERE NO RECENT WRITE-UPS FOR RUDDER OR BRAKE ISSUES.

Other reports on N42183 · 4

Matched to the same aircraft by N-number and date.