No fatalities

Jet Blast from Boeing 737 Damages Cessna 172 on Taxiway (N737AV)

Phoenix, AZ, US

On April 6, 1995, a Cessna 172N (registration N737AV) was involved in an aviation accident near Phoenix, AZ. No fatalities were reported. Investigators recorded the probable cause as: THE USE OF EXCESSIVE BREAK-AWAY THRUST BY THE BOEING 737 CREW. A FACTOR RELATED TO THE ACCIDENT WAS: IMPROPER PLANNING/DECISION BY THE CESSNA 172 PILOT BY ACCEPTING A CLEARANCE TO TAXI BEHIND THE BOEING 737 WITHOUT ASSURANCE THAT THE BOEING 737 CREW WOULD NOT… This summary draws on records from the U.S. National Transportation Safety Board (NTSB) historical archive; 1 related events involving the same aircraft type or operator are linked below.

Sourcesthe U.S. National Transportation Safety Board (NTSB) historical archivePrimary reportUpdated 2026-07-04Data APIEditorial standards

During engine tests, a Boeing 737 taxied on Runway 26L. A Cessna 172 on approach was cleared to exit at the same taxiway. The Boeing stopped then powered up, causing jet blast that substantially damaged the Cessna.

Incident Overview

Mechanics conducting engine tests in a Boeing 737 performed a high-speed taxi down Runway 26L. At the same time, a Cessna 172N, registration N737AV, was on final approach to land. The tower controller instructed the Boeing mechanics to exit the runway at midfield and "continue in the turn onto the parallel taxiway no delay off please."

Sequence of Events

One minute after the initial instruction, the mechanics requested clearance to proceed to the gate. The controller directed them to contact ground control. Following the turn onto the parallel taxiway, the Boeing came to a stop. The mechanics did not contact ground control until after the accident, which occurred 1 minute and 45 seconds later.

Meanwhile, the tower controller told the Cessna pilot to exit the runway at the same taxiway and then contact ground control. The controller stated that he cleared the Cessna based on the assumption that the Boeing would not stop. The Cessna exited the runway and stopped at the hold short line. The Cessna was then instructed to taxi northbound, crossing behind the Boeing.

As the Cessna began to move, the Boeing started powering up to resume taxiing. The jet blast from the Boeing resulted in substantial damage to the Cessna.

Statements from Mechanics

The mechanics reported that after turning onto the taxiway, they stopped and set the brakes while tuning the radio to the ground frequency. They said they then increased engine power to 40 to 50 percent N1 to begin taxiing again when they heard about "blasting the Cessna." At idle power, N1 was 21 percent.

Aircraft Specifications

A Boeing spokesman stated that break-away thrust for an empty Boeing 737 was 25 percent N1, while a fully loaded aircraft required 35 percent N1.

All Cessna 172 accidents →

Frequently asked questions

What happened in the 6 Apr 1995 Cessna 172N accident near Phoenix, AZ?

During engine tests, a Boeing 737 taxied on Runway 26L. A Cessna 172 on approach was cleared to exit at the same taxiway. The Boeing stopped then powered up, causing jet blast that substantially damaged the Cessna.

Were there any fatalities in the 6 Apr 1995 Cessna 172N accident?

No fatalities were recorded in this accident.

What aircraft was involved and where did it happen?

The accident on 6 Apr 1995 involved a Cessna 172N, registration N737AV, at Phoenix, AZ.

What was the probable cause of the accident?

THE USE OF EXCESSIVE BREAK-AWAY THRUST BY THE BOEING 737 CREW. A FACTOR RELATED TO THE ACCIDENT WAS: IMPROPER PLANNING/DECISION BY THE CESSNA 172 PILOT BY ACCEPTING A CLEARANCE TO TAXI BEHIND THE BOEING 737 WITHOUT ASSURANCE THAT THE BOEING 737 CREW WOULD NOT POWER UP.

Investigation report by the U.S. National Transportation Safety Board (NTSB) historical archive. Original record: https://carol.ntsb.gov/event/20001207X03313. This page is a structured re-presentation; facts and quotes are in the National Transportation Safety Board (NTSB), United States.