17 May 2009: CESSNA 172 M — Westwind Aviation Inc.

17 May 2009: CESSNA 172 M (N133GT) — Westwind Aviation Inc.

No fatalities • Burlington, WA, United States

Probable cause

Failure of the pilot to maintain adequate visual lookout during the approach.

— NTSB Determination

Accident narrative

HISTORY OF FLIGHT

On May 16, 2009, about 1800 Pacific daylight time, a Kilroy Pitts Model 12 amateur-built experimental airplane, N133GT, collided with a Cessna 172M, N70323, while both airplanes were attempting to land on runway 28 at the Skagit Airport, Burlington, Washington. The Cessna had touched down and was on the landing roll when the Pitts touched down on the Cessna’s left wing. Westwind Aviation, Inc., was operating the Cessna under the provisions of 14 Code of Federal Regulations (CFR) Part 135. The pilot/owner was operating the Pitts under the provisions of 14 CFR Part 91. In the Cessna, the airline transport pilot sustained minor injuries and the passenger was not injured; in the Pitts, both the airline transport pilot and the passenger were not injured. Both the airplanes sustained substantial damage. The Cessna departed from Sekiu Airport, Sekiu, Washington, on an air taxi on-demand passenger flight about 1720, with the intended destination of Burlington. The Pitts departed Jefferson County International Airport, Port Townsend, Washington, about 1730, with a planned destination of Burlington. Day visual meteorological conditions prevailed; the Cessna was on a visual flight rules (VFR) flight plan and the Pitts did not file a flight plan.

The Cessna pilot reported that as he entered the left downwind leg of the traffic pattern for runway 28, he observed the Pitts making a high-speed, low pass over the runway surface. After reaching a point about 3/4 down the runway, the Pitts began a steep, near vertical climb. It then appeared to turn left toward the downwind leg. The Cessna pilot made a radio transmission over the common traffic advisory (CTAF) frequency querying if the Pitts had his airplane in sight. There was no response.

The Cessna pilot continued maneuvering the airplane onto base and then final approach, making a radio transmission of his position at each leg. The airplane touched down normally and began to slow as the pilot applied brakes. While slowing, the pilot felt the impact of the Pitts landing on top of the left wing. The Pitts skidded out in front of the Cessna, sliding inverted and backwards down the runway; the Cessna skidded and nosed over.

The Pitts pilot reported that he completed the traffic pattern for runway 28 while communicating the airplane's positions on the CTAF. When the airplane was on short final, he opted to abort the landing due to traffic that had not yet cleared the runway. He aggressively ascended to traffic pattern altitude and began a left traffic pattern. While on the base leg and final approach he did not see any other airplanes, nor did he hear any other traffic over the radio. During the landing flare, the airplane lurched backward and upside down. Not until after egressing the airplane did he realize that he had contacted another airplane. The Cessna's left wing spar was bent.

ADDITIONAL INFORMATION

According to 14 CFR 91.113, Right-of-way rules: Except water operations, "Aircraft, while on final approach to land or while landing, have the right-of-way over other aircraft in flight or operating on the surface, except that they shall not take advantage of this rule to force an aircraft off the runway surface which has already landed and is attempting to make way for an aircraft on final approach."

The Skagit Regional Airport (BVS) is a public airport at a surveyed elevation of 144 feet. The airport features two asphalt runways, the longer of which is runway 10/28, which is 5,477 feet long by 100 feet wide. The airport is uncontrolled on weekends, which is when the accident occurred. The CTAF for the airport is 123.075 MHz.

Contributing factors

  • cause Pilot of other aircraft
  • cause Pilot

Conditions

Weather
VMC, wind 130/07kt, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.