 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZDC controller reported of an aircraft that transited in rvsm airspace; but was not qualified to be in that airspace. Controller reported that there was a loss of separation due to the aircraft not being rvsm equipped. Controller thought someone upstream should have verified if the aircraft was rvsm qualified.
| Attributes | |
| ACN | 1288624 |
| Time | |
| Date | 201508 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | ZDC.ARTCC |
| State Reference | VA |
| Environment | |
| Light | Night |
| Aircraft 1 | |
| Make Model Name | Military |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 4.1 |
| Events | |
| Anomaly | ATC Issue All Types Aircraft Equipment Problem Less Severe Conflict Airborne Conflict Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance |
Narrative:
I was working tyi sector during a high volume; weather event session. No d-side. Yorktown sector called me on the land line to coordinate a hand off for aircraft X. They stated that the aircraft was verified level at FL360 and the pilot said all equipment was operational. It turns out that the flight was a co-related primary target in class a airspace. This disqualifies the aircraft to operate in rvsm airspace. I did not verify with the pilot when they checked in assuming that the previous controller had taken the correct protocols. Not to mention they had an aircraft 1;000 feet above that I had just fed them. Apparently this aircraft transitted through 4 or 5 ZDC sectors before it made it to tyi. I was told after the fact by a manager that the aircraft was not eligible for rvsm airspace. The aircraft transited through tyi as if it was rvsm capable. There were no conflicts while I was on position. A better understanding of why an aircraft is not capable of rvsm is necessary. I was always under assumption that if the aircraft states they are capable; of rvsm than they are. Clearly this is not the case.
Original NASA ASRS Text
Title: ZDC Controller reported of an aircraft that transited in RVSM airspace; but was not qualified to be in that airspace. Controller reported that there was a loss of separation due to the aircraft not being RVSM equipped. Controller thought someone upstream should have verified if the aircraft was RVSM qualified.
Narrative: I was working TYI sector during a high volume; weather event session. No D-side. Yorktown sector called me on the land line to coordinate a hand off for Aircraft X. They stated that the aircraft was verified level at FL360 and the pilot said all equipment was operational. It turns out that the flight was a co-related primary target in Class A airspace. This disqualifies the aircraft to operate in RVSM airspace. I did not verify with the pilot when they checked in assuming that the previous controller had taken the correct protocols. Not to mention they had an aircraft 1;000 feet above that I had just fed them. Apparently this aircraft transitted through 4 or 5 ZDC sectors before it made it to TYI. I was told after the fact by a manager that the aircraft was not eligible for RVSM airspace. The aircraft transited through TYI as if it was RVSM capable. There were no conflicts while I was on position. A better understanding of why an aircraft is not capable of RVSM is necessary. I was always under assumption that if the aircraft states they are capable; of RVSM than they are. Clearly this is not the case.
Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.