 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Revised altitude not passed to next facility resulting in MTR crossing in front of mlt at same altitude.
| Attributes | |
| ACN | 106944 |
| Time | |
| Date | 198903 |
| Day | Fri |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | atc facility : mxw |
| State Reference | CA |
| Altitude | msl bound lower : 11000 msl bound upper : 11000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : zoa tracon : sac |
| Operator | other |
| Make Model Name | Military Trainer |
| Flight Phase | cruise other |
| Route In Use | enroute : direct |
| Flight Plan | IFR |
| Aircraft 2 | |
| Operator | other |
| Make Model Name | Military Transport |
| Flight Phase | cruise other |
| Route In Use | enroute : direct |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Qualification | controller : radar |
| Experience | controller radar : 2 |
| ASRS Report | 106944 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Qualification | controller : radar |
| Events | |
| Anomaly | conflict : airborne less severe non adherence : required legal separation non adherence : published procedure |
| Independent Detector | other flight crewa |
| Resolutory Action | none taken : detected after the fact |
| Consequence | faa : investigated |
| Miss Distance | horizontal : 6000 vertical : 500 |
| Supplementary | |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Inter Facility Coordination Failure Operational Error |
Narrative:
I was working sector 40 position when MTR checked on. The aircraft was supposed to be at 5000', but earlier, sacramento approach assigned a wrong altitude of 11000'. The first sector at ZOA did not catch the wrong altitude and then handed him off to me with a controller entered 8000' in the data block, which means the aircraft is level at that altitude. When MTR checked on he was broken and garbled and I did not hear the altitude clearly. I looked up at the data block, saw the 8000', and of course thought that was his altitude he reported at. My sector is only 8000' and below and he was the only aircraft in the northern area of my sector. The sector above me had mlt at 11000' who reported a MTR pretty close. The controller told me that I might want to check the MTR's altitude, which I did.
Original NASA ASRS Text
Title: REVISED ALT NOT PASSED TO NEXT FAC RESULTING IN MTR CROSSING IN FRONT OF MLT AT SAME ALT.
Narrative: I WAS WORKING SECTOR 40 POS WHEN MTR CHKED ON. THE ACFT WAS SUPPOSED TO BE AT 5000', BUT EARLIER, SACRAMENTO APCH ASSIGNED A WRONG ALT OF 11000'. THE FIRST SECTOR AT ZOA DID NOT CATCH THE WRONG ALT AND THEN HANDED HIM OFF TO ME WITH A CTLR ENTERED 8000' IN THE DATA BLOCK, WHICH MEANS THE ACFT IS LEVEL AT THAT ALT. WHEN MTR CHKED ON HE WAS BROKEN AND GARBLED AND I DID NOT HEAR THE ALT CLEARLY. I LOOKED UP AT THE DATA BLOCK, SAW THE 8000', AND OF COURSE THOUGHT THAT WAS HIS ALT HE RPTED AT. MY SECTOR IS ONLY 8000' AND BELOW AND HE WAS THE ONLY ACFT IN THE NORTHERN AREA OF MY SECTOR. THE SECTOR ABOVE ME HAD MLT AT 11000' WHO RPTED A MTR PRETTY CLOSE. THE CTLR TOLD ME THAT I MIGHT WANT TO CHK THE MTR'S ALT, WHICH I DID.
Data retrieved from NASA's ASRS site as of August 2007 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.