13 Feb 20269:15 reconstruction61K views

This jet causes Multiple Close Calls amidst Disruption and confusion

In June 2019, Global Express VistaJet 868 departed Seattle Boeing Field under VFR and quickly became involved in a sequence of confusing traffic instructions. The crew read back a clearance intended for another aircraft, entered a traffic pattern, requested an IFR departure to Athens and then had to maneuver in response to a Boeing 757 climbing north from Seattle-Tacoma. The aircraft ultimately exited the Class D area and contacted Seattle Departure for its IFR clearance.

Timeline

June 2019 —

VistaJet 868, a Global Express, prepared to depart Boeing Field.

Initial departure —

The aircraft departed Runway 32L under VFR and read back instructions that had been intended for another aircraft in the pattern.

Traffic conflict —

The tower issued an urgent turn instruction because a Boeing 757 was climbing northbound from Seattle-Tacoma.

After the immediate conflict —

The tower asked VistaJet 868 for its intentions.

IFR request —

The crew requested an IFR departure to Athens.

Tower response —

The tower told the crew to land if they wanted the IFR clearance; the crew said they could not land for several hours because of weight.

Resolution —

The aircraft was vectored around the Class D airspace and later handed to Seattle Departure to obtain the IFR clearance while exiting the area.

The first problem was a wrong readback

contemporary reporting says VistaJet 868 read back instructions intended for a Cessna in the pattern. That created an early mismatch between what the controller intended and what the crew believed it had received.

A second aircraft was already climbing

The tower then issued a hard-right-turn instruction because a Boeing 757 was climbing northbound from Seattle-Tacoma. The available recording context shows that the controller was trying to keep the Global Express away from that traffic while also determining what the jet intended to do next.

The IFR request added another layer

VistaJet 868 then requested an IFR departure to Athens. The tower’s proposed solution was to land first, but the crew said they could not do so for several hours because of the aircraft’s weight. The aircraft remained airborne in the local area and was eventually routed around the Class D airspace before contacting Seattle Departure.

Do not turn the exchange into a blame finding

The source demonstrates confusion and multiple close approaches, but it does not provide a formal investigation assigning sole fault to either side. The documented communications and aircraft movements are described without treating the controller’s frustration or the pilot’s readbacks as an official finding.

The documented record

“HARD RIGHT TURN NOW.” — the Seattle tower transmission reproduced in the ATC recording

Conclusion

The event developed through mismatched expectations: a readback of another aircraft’s instructions, a nearby departure, a later IFR request and disagreement about landing before receiving the clearance. the documented record supports the sequence but not a formal blame determination, and no final cause has been assigned.

Aircraft: B757
Airports: SEA (Seattle-Tacoma)
Reconstruction: 9:15

Sources

Source video: https://www.youtube.com/watch?v=zWVgCDO5tGY PPRuNe discussion of the June 2019 ATC recording: https://www.pprune.org/rumours-news/623395-vistajet-vjt868-causing-confusion-sea-2.html

Audio from the original air traffic control recording, sourced from public recordings and released investigation records. The reconstruction, animation and written account are our own.