SEA07LA050

NTSB accident investigation · Piper PA-28R-180 · Fresno, CA · December 21, 2006

Accident · No injuriesLimited investigationFinal report
Date
December 20, 2006, 17:00 local (Dec 21, 2006, 01:00 UTC)
Place
Fresno, CA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Unknown
Aircraft
N4666JPiper PA-28R-180
Status
Completed · report April 25, 2007
Report
Approved by Office Director
Parties
Federal Aviation Administration
FAA report
20061220028969A
Case key
65179

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

The NTSB’s determination of the probable cause, and any contributing factors.

The design stress limits of the airframe were exceeded by an unknown pilot.

Analysis

No damage to the airplane was detected prior to the flight instructor being checked out in the airplane, as well as before the cross-country instructional flight which followed the check out. After the completion of the cross-country flight wrinkled skin on top of both wings was discovered. The instructor stated that the damage was not a result of anything that had transpired during the cross-country flight. Interviews conducted by the FAA with numerous pilots who had recently flown the airplane failed to reveal who was responsible for the damage or how it was caused.

Factual narrative

On December 20, 2006, approximately 1700 Pacific standard time, substantial damage to a Piper PA-28R-180, N4666J, was discovered while the aircraft was being refueled after the completion of a cross-country instructional flight at the Fresno Chandler Executive Airport (FCH), Fresno, California. The airplane is registered to Memley Aviation Inc., of Fresno, and was operated by a certificated flight instructor. The date, time, and circumstances, which resulted in the aircraft being damaged to the aircaft is unknown.

In a telephone interview and in a written statement submitted to the NTSB investigator-in-charge (IIC), the flight instructor reported that on the day the damage was discovered he had undergone a checkout in the airplane, followed by a cross-country flight with a pilot-rated student. The pilot stated that prior to the checkout flight the check pilot told him that he had already done a preflight, but that the instructor could do one if he wished. The instructor reported that the did a "quick walk around" but did not notice damage to the landing gear or to the top of the wings. The instructor stated, "Had I done a full preflight myself I would have seen it." The instructor reported that after the checkout flight was completed he and his student flew to the Santa Monica Municipal airport (SMO), followed by a return flight to FCH. The instructor further reported that after landing at FCH and during refueling, the airplane's owner observed wrinkled skin on the top of both wings directly over the main landing gear, with wing rivets displace/popped out their secured riveted positions. The instructor stated that after being apprised of the damage, "...I knew that nothing that transpired during the course of my time in 66J could have come close to causing that kind of damage."

Interviews conducted by Federal Aviation Administration personnel with several pilots who had recently flown the accident airplane failed to reveal who was responsible for the damage, or how the damage occurred.

Sequence of events

NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.

Miscellaneous/otherUnknown
Design stress limits of aircraft - exceededUnknownCause

Aircraft

Registration
N4666J
Reported as
Piper PA-28R-180
Category
Airplane
Serial number
28R-30565
Airframe hours
4,422
Engine
Lycoming IO-360, 200 horsepower, reciprocating
Damage
Substantial damage
Registered owner
Memly Aviation Inc.
Airworthiness certificate
Standard, Normal
Last inspection
AAIP · November 1, 2006 · 16 hours before
Flight plan
Unknown
Airport
FCH · Fresno Chandler Executive

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.