Incident Overview
A student pilot flying solo was taxiing onto runway 30 for takeoff when his aircraft was affected by the propeller blast from a Horizon Air DHC-8 that was conducting a maintenance engine run in a runup area northeast of the approach end of runway 30.
Sequence of Events
After completing his preflight checklist, the student pilot waited, believing the DHC-8 was about to depart. When it did not, he requested and received takeoff clearance for runway 30 from the tower controller, who did not issue any cautionary advisories regarding the DHC-8 activity.
As the student pilot began moving toward the runway, he reported being more than halfway past behind the Horizon aircraft when its engines were revved. The propeller blast forced his aircraft to tip left and forward, causing the wingtip and propeller to strike the taxiway surface. The aircraft continued to be buffeted by the blast for several more minutes as the DHC-8 continued its engine run.
Communication and Response
The tower was unable to reach the DHC-8 on the radio. The DHC-8 crew, consisting of two Horizon Air mechanics, continued the engine run until an airport operations vehicle, dispatched by the tower, approached and signaled them. Around that time, the tower re-established radio contact and instructed the crew to reduce engine power. In interviews with an FAA inspector, the mechanics stated they did not know how or why they lost radio contact with the tower.
Regulatory Context
FAA Order 7110.65N, "Air Traffic Control", directs controllers to issue wake turbulence cautionary information, including the words "jet blast," "propwash," or "rotorwash," to any aircraft on the movement area if they believe wake turbulence may have an adverse effect. However, the order also states that because wake turbulence is unpredictable, the controller is not responsible for anticipating its existence or effect. A review of FAA Air Traffic Bulletins found no information on jet blast or prop blast hazards.