20010908025439A

Accident · No damage

FAA accident report · Cessna 172N · Pasco, WA · September 8, 2001

Date
September 8, 2001 · 07:15 local
Place
Pasco, WA
Airport
Tri Cities Airport
Operating rules
General operating rules (Part 91)
Damage
No damage
Aircraft
N426SK
NTSB investigation
NTSBSEA01LA169
Reported as
Cessna 172N
Pilot’s certificate
Student

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) Pilot taxied out and completed runup adjacent to DHC-8 aircraft. Pilot waited for 816PH to depart, believing it was a passenger flight preparing to leave. When it did not depart pilot called for, and received, a takeoff clearance. The pilot did not know that the DHC-8 was controlled by maintenance personnel, conducting a maintenance power test. As there was not enough room to taxi in front of the DHC-8 the pilot taxied behind the aircraft. The pilot indicated that as he began to taxi the DHC-8 was at low power, but as he taxied behind the aircraft the power suddently increased on one engine, and his aircraft was blown over onto the left wing and nose of the aircraft, resulting in substantial damage. Subsequent investigation yielded that the maintenance crew aboard the DHC-8 failed to maintain radio communication with the tower, and was at no time aware of the Cessna 172 aircraft in their proximity. An airport fire truck was dispatched to the DHC-8 to get their attention, flashing lights until the crew looked up and responded. The maintenance crew was then notified that the tower had been trying to contact them.

As the FAA filed it

(-23) PILOT TAXIED OUT AND COMPLETED RUNUP ADJACENT TO DHC-8 AIRCRAFT. PILOT WAITED FOR 816PH TO DEPART, BELIEVING IT WAS A PASSENGER FLIGHT PREPARING TO LEAVE. WHEN IT DID NOT DEPART PILOT CALLED FOR, AND RECEIVED, A TAKEOFF CLEARANCE. THE PILOT DID NOT KNOW THAT THE DHC-8 WAS CONTROLLED BY MAINTENANCE PERSONNEL, CONDUCTING A MAINTENANCE POWER TEST. AS THERE WAS NOT ENOUGH ROOM TO TAXI IN FRONT OF THE DHC-8 THE PILOT TAXIED BEHIND THE AIRCRAFT. THE PILOT INDICATED THAT AS HE BEGAN TO TAXI THE DHC-8 WAS AT LOW POWER, BUT AS HE TAXIED BEHIND THE AIRCRAFT THE POWER SUDDENTLY INCREASED ON ONE ENGINE, AND HIS AIRCRAFT WAS BLOWN OVER ONTO THE LEFT WING AND NOSE OF THE AIRCRAFT, RESULTING IN SUBSTANTIAL DAMAGE. SUBSEQUENT INVESTIGATION YIELDED THAT THE MAINTENANCE CREW ABOARD THE DHC-8 FAILED TO MAINTAIN RADIO COMMUNICATION WITH THE TOWER, AND WAS AT NO TIME AWARE OF THE CESSNA 172 AIRCRAFT IN THEIR PROXIMITY. AN AIRPORT FIRE TRUCK WAS DISPATCHED TO THE DHC-8 TO GET THEIR ATTENTION, FLASHING LIGHTS UNTIL THE CREW LOOKED UP AND RESPONDED. THE MAINTENANCE CREW WAS THEN NOTIFIED THAT THE TOWER HAD BEEN TRYING TO CONTACT THEM.

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 N426SK · 2

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