37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 691409 |
Time | |
Date | 200603 |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | navaid : lax.vortac |
State Reference | CA |
Altitude | msl bound lower : 38000 msl bound upper : 39000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zla.artcc tower : ord.tower |
Operator | common carrier : air carrier |
Make Model Name | B737 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | cruise : level |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | artcc : zla.artcc |
Make Model Name | Gulfstream III |
Flight Phase | climbout : intermediate altitude |
Flight Plan | IFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : radar |
Qualification | controller : radar |
Experience | controller radar : 17 controller time certified in position1 : 12 |
ASRS Report | 691409 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Events | |
Anomaly | non adherence : required legal separation |
Resolutory Action | none taken : detected after the fact |
Consequence | faa : investigated |
Miss Distance | horizontal : 0 vertical : 1000 |
Supplementary | |
Problem Areas | ATC Human Performance |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Operational Error |
Narrative:
Aircraft Y was negative rvsm but had filed /Q indicating to controllers he was rvsm certified. I applied rvsm separation between aircraft X and aircraft Y. I was later advised I had an operational error since separation should have been 2000 ft vertical. The aircraft advised on frequency that he was 'negative rvsm' once but I did not hear it or acknowledge it and the pilot did not repeat. I am not sure how the error was discovered. Controllers learn to trust the display on their scope and the display indicated there was no loss of separation. The pilot may have assumed controllers were aware of his rvsm status even though it was not acknowledged. In addition; it is imperative that pilots file the correct rvsm status of the aircraft/crew. Much like controllers cannot assume pilots have heard the clrncs unless acknowledged or read back; pilots should do the same with important flight information.
Original NASA ASRS Text
Title: ZLA CTLR HAS OPERROR WHEN RVSM SEPARATION STANDARD IS APPLIED TO NON RVSM CAPABLE ACFT.
Narrative: ACFT Y WAS NEGATIVE RVSM BUT HAD FILED /Q INDICATING TO CTLRS HE WAS RVSM CERTIFIED. I APPLIED RVSM SEPARATION BTWN ACFT X AND ACFT Y. I WAS LATER ADVISED I HAD AN OPERROR SINCE SEPARATION SHOULD HAVE BEEN 2000 FT VERT. THE ACFT ADVISED ON FREQ THAT HE WAS 'NEGATIVE RVSM' ONCE BUT I DID NOT HEAR IT OR ACKNOWLEDGE IT AND THE PLT DID NOT REPEAT. I AM NOT SURE HOW THE ERROR WAS DISCOVERED. CTLRS LEARN TO TRUST THE DISPLAY ON THEIR SCOPE AND THE DISPLAY INDICATED THERE WAS NO LOSS OF SEPARATION. THE PLT MAY HAVE ASSUMED CTLRS WERE AWARE OF HIS RVSM STATUS EVEN THOUGH IT WAS NOT ACKNOWLEDGED. IN ADDITION; IT IS IMPERATIVE THAT PLTS FILE THE CORRECT RVSM STATUS OF THE ACFT/CREW. MUCH LIKE CTLRS CANNOT ASSUME PLTS HAVE HEARD THE CLRNCS UNLESS ACKNOWLEDGED OR READ BACK; PLTS SHOULD DO THE SAME WITH IMPORTANT FLT INFO.
Data retrieved from NASA's ASRS site as of January 2009 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.