Issue traffic information to the aircraft listed in subparagraph a whose targets appear likely to merge unless
the
aircraft are separated by more than the appropriate vertical separation minima.
“United Sixteen and American Twenty-Five, traffic twelve o'clock, one zero miles, opposite direction,
eastbound Seven Thirty-Seven at flight level three three zero, westbound Airbus Three Twenty at flight level
three two zero.”
When both aircraft in subparagraph b are in RVSM airspace, and vertically separated by 1,000 feet, and either
pilot
reports they are unable to maintain RVSM due to turbulence or mountain wave, use vectors to prevent the targets
from merging.
EXAMPLE
“Delta One Twenty Three, fly heading two niner zero, vector for traffic. Traffic twelve o'clock, one zero
miles, opposite direction, Seven Thirty-Seven, eastbound at flight level three one zero.”
If the pilot requests, vector their aircraft to avoid merging targets with the previously issued traffic.
NOTE: Because aircraft closure rates can be rapid, issue traffic with enough time for the pilot to decide if a
vector is necessary.
If unable to provide vector service, inform the pilot.
NOTE: The phraseology “Unable RVSM due turbulence (or mountain wave)” is only intended for severe turbulence
or other weather encounters with altitude deviations of approximately 200 feet or more.
Much more information and resources are available to registered users, so sign up now! Also, please read our site usage guidelines. These will help you get the most out of the site. Thanks!