Welcome to Flightinfo.com

  • Register now and join the discussion
  • Friendliest aviation Ccmmunity on the web
  • Modern site for PC's, Phones, Tablets - no 3rd party apps required
  • Ask questions, help others, promote aviation
  • Share the passion for aviation
  • Invite everyone to Flightinfo.com and let's have fun

TCAS "RA" and RVSM

Welcome to Flightinfo.com

  • Register now and join the discussion
  • Modern secure site, no 3rd party apps required
  • Invite your friends
  • Share the passion of aviation
  • Friendliest aviation community on the web

vlamgat

Member
Joined
Dec 12, 2002
Posts
10
While flying at FL330, complying with RVSM you get a TCAS RA. I'm sure your reaction will be the same as if you where at any other FL and you would follow the RA instructions. But I am looking for the exact wording or the reg in the FAR/AIM (if any) that would aply to this situation.
 
"Center, Boeing 123, TCAS climb / descent" No reference, what I was told.:confused: Don't think it really matters whether or not your in RVSM, the important part is getting back to your assigned altitude after you are clear traffic.
 
Last edited:
from the ATC Book, 7110.65
http://www.faa.gov/ATpubs/Atc/Chp2/atc0201.html

2-1-27. TCAS RESOLUTION ADVISORIES


a. When an aircraft under your control jurisdiction informs you that it is responding to a TCAS Resolution Advisory (RA), do not issue control instructions that are contrary to the RA procedure that a crew member has advised you that they are executing. Provide safety alerts regarding terrain or obstructions and traffic advisories for the aircraft responding to the RA and all other aircraft under your control jurisdiction, as appropriate.​

b.
Unless advised by other aircraft that they are also responding to a TCAS RA, do not assume that other aircraft in the proximity of the responding aircraft are involved in the RA maneuver or are aware of the responding aircraft's intended maneuvers. Continue to provide control instructions, safety alerts, and traffic advisories as appropriate to such aircraft.​

c.
Once the responding aircraft has begun a maneuver in response to an RA, the controller is not responsible for providing standard separation between the aircraft that is responding to an RA and any other aircraft, airspace, terrain or obstructions. Responsibility for standard separation resumes when one of the following conditions are met:​

1.
The responding aircraft has returned to its assigned altitude, or​

2.
A crew member informs you that the TCAS maneuver is completed and you observe that standard separation has been reestablished, or​

3.
The responding aircraft has executed an alternate clearance and you observe that standard separation has been reestablished.​

NOTE-

1.
AC 120-55A, Air Carrier Operational Approval and Use of TCAS II, suggests pilots use the following phraseology to notify controllers during TCAS events. When a TCAS RA may affect an ATC clearance, inform ATC when beginning the maneuver, or as soon as workload permits.

EXAMPLE-

1. "New York Center, United 321, TCAS climb."

NOTE-

2. When the RA has been resolved, the flight crew should advise ATC they are returning to their previously assigned clearance or subsequent amended clearance.

EXAMPLE-

2. "New York Center, United 321, clear of conflict, returning to assigned altitude."

2-1-28. RVSM OPERATIONS

Controller responsibilities shall include but not be limited to the following:​

a.
Non-RVSM aircraft operating in RVSM airspace.​

1.
Ensure non-RVSM aircraft are not permitted in RVSM airspace unless they meet the criteria of excepted aircraft and are previously approved by the operations supervisor/controller-in-charge (CIC). The following aircraft are excepted: DOD, Lifeguard, manufacturer aircraft being flown for development/certification, and Foreign State aircraft. These exceptions are accommodated on a workload or traffic-permitting basis.​

NOTE-

The operations supervisor/CIC is responsible for system acceptance of a non-RVSM aircraft beyond the initial sector to sector coordination following the pilot request to access the airspace. Operations supervisor/CIC responsibilities are defined in FAA Order 7210.3, Chapter 6, Section 9, Reduced Vertical Separation Minimum (RVSM).

2.
A non-RVSM exception designated by the DOD for special consideration via the DOD Priority Mission website shall be referred to as a STORM flight.​

3.
Ensure sector-to-sector coordination for all non-RVSM aircraft operations within RVSM airspace.​

4.
Inform the operational supervisor/CIC when a non-RVSM exception flight is denied clearance into RVSM airspace or is removed from RVSM airspace.​

b.
Non-RVSM aircraft transitioning RVSM airspace.​
Ensure that operations supervisors/CICs are made aware when non-RVSM aircraft are transitioning through RVSM airspace.​

c.
Apply appropriate separation standards and remove any aircraft from RVSM airspace that advises it is unable RVSM due to equipment while en route.​

d.
Use "negative RVSM" in all verbal ground- to-ground communications involving non-RVSM aircraft while cleared to operate within RVSM airspace.​

EXAMPLE-

"Point out Baxter21 climbing to FL 360, negative RVSM."

e.
For the following situations, use the associated phraseology:​

1.
To deny clearance into RVSM airspace.​

PHRASEOLOGY-

"UNABLE CLEARANCE INTO RVSM AIRSPACE."

2.
To request a pilot to report when able to resume RVSM.​
PHRASEOLOGY-
"REPORT ABLE TO RESUME RVSM."

f.
In the event of a change to an aircraft's navigational capability amend the equipment suffix in order to properly identify non-RVSM aircraft on the controller display.

2-1-29. TERRAIN AWARENESS WARNING SYSTEM (TAWS) ALERTS

a. When an aircraft under your control jurisdiction informs you that it is responding to a TAWS (or other on-board low altitude) alert, do not issue control instructions that are contrary to the TAWS procedure that a crew member has advised you that they are executing. Provide safety alerts regarding terrain or obstructions and traffic advisories for the aircraft responding to the TAWS alert and all other aircraft under your control jurisdiction, as appropriate.​

b.
Once the responding aircraft has begun a maneuver in response to TAWS alert, the controller is not responsible for providing standard separation between the aircraft that is responding to a TAWS alert and any other aircraft, airspace, terrain or obstructions. Responsibility for standard separation resumes when one of the following conditions are met:​

1.
The responding aircraft has returned to its assigned altitude, or​

2.
A crew member informs you that the TAWS maneuver is completed and you observe that standard separation has been reestablished, or​

3.
The responding aircraft has executed an alternate clearance and you observe that standard separation has been reestablished.


- praise be to the Administrator.
 
If you get an RA while you are in RVSM airspace you are required to give a written report. This is not optional.

To keep from this happening, the FAA suggests that you climb or descend at 1000ft/min within the last 1000 feet of your assigned altitude to keep from giving ta/ra's
 
Last edited:
We had an RA the other day at FL310 while crossing the Atlantic at about 30W. I immediately climbed and when we got the "clear of conflict" call descended back to 310. We marked the pt. and time and called Santa Maria on the HF and told them what happened, and we heard the UPS plane call in shortly thereafter reporting they also had to comply with an RA. Santa Maria said they were filing a report and we also filed a report. FWIW our mode C had crapped out and was transmitting the wrong altitude so we ended up coasting in with the tcas off.
 

Latest posts

Latest resources

Back
Top