20020313003329A

Accident · No damage

FAA accident report · Piper PA-31-350 · Fairbanks, AK · March 13, 2002

Date
March 13, 2002 · 15:53 local
Place
Fairbanks, AK
Airport
Fairbanks International
Operating rules
Air taxi and commuter (Part 135)
Operator
WVBA
Damage
No damage
Aircraft
N3527U
NTSB investigation
NTSBANC02LA022
Reported as
Piper PA31350

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.

(.19) On March 13, 2002, about 1553 Alaska standard time, a Piper PA-31-350 airplane, N3527U, sustained substantial damage during an inadvertent wheels-up landing, at the Fairbanks International Airport, Fairbanks, Alaska. The airplane was being operated as a visual flight rules (VFR) scheduled passenger flight under title 14, CFR part 135, when the accident occurred. The airplane was operated by warbelow air ventures, inc., of Fairbanks, as flight 605. The certificated airline transport pilot and the eight passengers were not injured. Visual meteorological conditions prevailed, and the winds were light and variable at the time of the accident. A company VFR flight plan was active. The flight originated at the fort yukon airport, fort yukon, Alaska, about 1503. During a telephone conversation with the national transportation safety board (NTSB) investigator-in-charge (iic), on March 14, the pilot said as he entered the pattern, he was told by the tower to cross over and enter right traffic for runway 1. The tower then told him he would have to extend downwind because of traffic. The pilot said he made a conscious decision not to put the landing gear down at the usual point because of the request to extend his pattern. He said as he started to extend his pattern, the tower asked him to expedite a base turn, and "keep it tight". The pilot said on the base leg, he again failed to complete his checklist. He said on the final leg of his approach, the airplane behind him said they were too close, and they were going to go around. In the confusion, he said he never completed his before landing checklist, and landed the airplane with the landing gear retracted. The pilot said that fatigue added to his confusion, which lead to the accident. During a telephone conversation with the iic on March 14, the director of maintenance for the operator said the forward third of the longitudinal stringers and several bulkheads of the fuselage will have to be replaced, due to damage incurred during the accident. Once the airplane was raised off of the runway, the landing gear functioned normally, and the 3 green landing gear warning lights illuminated. (-23) busy traffic pattern, deviation from standard pattern, failed to complete landing check list, failed to extend landing gear and landed with landing gear up.

As the FAA filed it

(.19) ON MARCH 13, 2002, ABOUT 1553 ALASKA STANDARD TIME, A PIPER PA-31-350 AIRPLANE, N3527U, SUSTAINED SUBSTANTIAL DAMAGE DURING AN INADVERTENT WHEELS-UP LANDING, AT THE FAIRBANKS INTERNATIONAL AIRPORT, FAIRBANKS, ALASKA. THE AIRPLANE WAS BEING OPERATED AS A VISUAL FLIGHT RULES (VFR) SCHEDULED PASSENGER FLIGHT UNDER TITLE 14, CFR PART 135, WHEN THE ACCIDENT OCCURRED. THE AIRPLANE WAS OPERATED BY WARBELOW AIR VENTURES, INC., OF FAIRBANKS, AS FLIGHT 605. THE CERTIFICATED AIRLINE TRANSPORT PILOT AND THE EIGHT PASSENGERS WERE NOT INJURED. VISUAL METEOROLOGICAL CONDITIONS PREVAILED, AND THE WINDS WERE LIGHT AND VARIABLE AT THE TIME OF THE ACCIDENT. A COMPANY VFR FLIGHT PLAN WAS ACTIVE. THE FLIGHT ORIGINATED AT THE FORT YUKON AIRPORT, FORT YUKON, ALASKA, ABOUT 1503. DURING A TELEPHONE CONVERSATION WITH THE NATIONAL TRANSPORTATION SAFETY BOARD (NTSB) INVESTIGATOR-IN-CHARGE (IIC), ON MARCH 14, THE PILOT SAID AS HE ENTERED THE PATTERN, HE WAS TOLD BY THE TOWER TO CROSS OVER AND ENTER RIGHT TRAFFIC FOR RUNWAY 1. THE TOWER THEN TOLD HIM HE WOULD HAVE TO EXTEND DOWNWIND BECAUSE OF TRAFFIC. THE PILOT SAID HE MADE A CONSCIOUS DECISION NOT TO PUT THE LANDING GEAR DOWN AT THE USUAL POINT BECAUSE OF THE REQUEST TO EXTEND HIS PATTERN. HE SAID AS HE STARTED TO EXTEND HIS PATTERN, THE TOWER ASKED HIM TO EXPEDITE A BASE TURN, AND "KEEP IT TIGHT". THE PILOT SAID ON THE BASE LEG, HE AGAIN FAILED TO COMPLETE HIS CHECKLIST. HE SAID ON THE FINAL LEG OF HIS APPROACH, THE AIRPLANE BEHIND HIM SAID THEY WERE TOO CLOSE, AND THEY WERE GOING TO GO AROUND. IN THE CONFUSION, HE SAID HE NEVER COMPLETED HIS BEFORE LANDING CHECKLIST, AND LANDED THE AIRPLANE WITH THE LANDING GEAR RETRACTED. THE PILOT SAID THAT FATIGUE ADDED TO HIS CONFUSION, WHICH LEAD TO THE ACCIDENT. DURING A TELEPHONE CONVERSATION WITH THE IIC ON MARCH 14, THE DIRECTOR OF MAINTENANCE FOR THE OPERATOR SAID THE FORWARD THIRD OF THE LONGITUDINAL STRINGERS AND SEVERAL BULKHEADS OF THE FUSELAGE WILL HAVE TO BE REPLACED, DUE TO DAMAGE INCURRED DURING THE ACCIDENT. ONCE THE AIRPLANE WAS RAISED OFF OF THE RUNWAY, THE LANDING GEAR FUNCTIONED NORMALLY, AND THE 3 GREEN LANDING GEAR WARNING LIGHTS ILLUMINATED. (-23) BUSY TRAFFIC PATTERN, DEVIATION FROM STANDARD PATTERN, FAILED TO COMPLETE LANDING CHECK LIST, FAILED TO EXTEND LANDING GEAR AND LANDED WITH LANDING GEAR UP.

NTSB investigation

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

Other reports on N3527U · 4

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