37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 166014 |
Time | |
Date | 199012 |
Day | Tue |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | atc facility : csg |
State Reference | GA |
Altitude | msl bound lower : 22000 msl bound upper : 22500 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : ztl |
Operator | common carrier : air carrier |
Make Model Name | Light Transport, Low Wing, 2 Turboprop Eng |
Navigation In Use | Other |
Flight Phase | descent 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 | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp |
Experience | flight time last 90 days : 260 flight time total : 4300 flight time type : 2000 |
ASRS Report | 166014 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Events | |
Anomaly | conflict : airborne less severe non adherence : published procedure non adherence : required legal separation |
Independent Detector | other controllera |
Resolutory Action | none taken : insufficient time |
Consequence | faa : reviewed incident with flight crew |
Miss Distance | horizontal : 18000 vertical : 500 |
Supplementary | |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Operational Error |
Narrative:
Air carrier X about 120 NM north of tlh on J43 at FL230, en route to tlh from atz. I heard a couple of scratchy xmissions, and then heard our numbers. The controller sounded pretty excited, and told us to descend to FL220. The aircraft, an light transport was on autoplt and I hit the descent mode. The controller said we had traffic at 2 O'clock and 3 mi nebnd at FL230. Within seconds, we had the traffic, a large mlt Y. When we were descending through 22500', the controled asked us to verify we were at FL220. The captain told him we were leveling at FL220 and head the traffic in sight. The controled came back and said 'when I say descend, I mean now, not 5 mins later!' the captain replied that we had started down when he told us to and that his xmissions were very scratchy. One or two other pilots in different aircraft also told the controller at this time that his xmissions were scratchy. When we were clear of the traffic, the controller had us climb back to FL230. The controller obviously was caught off guard by two converging aircraft at the same altitude. Maybe an alarm went off. Probably one reason he was difficult to understand is that he was so excited. He obviously waited too late to contact us, but if he was having trouble getting us, why didn't he tell the other aircraft to descend? When the controller had first tried to contact us, I was just sitting there monitoring the aircraft. But perhaps if I had been more alert, I would have caught his first transmission. But alertness is hard to achieve after being on duty the previous day for 15 hours and flying over 8 hours in bad WX. With only an 8 hour overnight and into. Our 8TH hour of duty on this day, even staying awake can be a challenge.
Original NASA ASRS Text
Title: ACR X HAD LESS THAN STANDARD SEPARATION FROM MLT Y. SYSTEM ERROR.
Narrative: ACR X ABOUT 120 NM N OF TLH ON J43 AT FL230, ENRTE TO TLH FROM ATZ. I HEARD A COUPLE OF SCRATCHY XMISSIONS, AND THEN HEARD OUR NUMBERS. THE CTLR SOUNDED PRETTY EXCITED, AND TOLD US TO DSND TO FL220. THE ACFT, AN LTT WAS ON AUTOPLT AND I HIT THE DSNT MODE. THE CTLR SAID WE HAD TFC AT 2 O'CLOCK AND 3 MI NEBND AT FL230. WITHIN SECS, WE HAD THE TFC, A LARGE MLT Y. WHEN WE WERE DSNDING THROUGH 22500', THE CTLED ASKED US TO VERIFY WE WERE AT FL220. THE CAPT TOLD HIM WE WERE LEVELING AT FL220 AND HEAD THE TFC IN SIGHT. THE CTLED CAME BACK AND SAID 'WHEN I SAY DSND, I MEAN NOW, NOT 5 MINS LATER!' THE CAPT REPLIED THAT WE HAD STARTED DOWN WHEN HE TOLD US TO AND THAT HIS XMISSIONS WERE VERY SCRATCHY. ONE OR TWO OTHER PLTS IN DIFFERENT ACFT ALSO TOLD THE CTLR AT THIS TIME THAT HIS XMISSIONS WERE SCRATCHY. WHEN WE WERE CLR OF THE TFC, THE CTLR HAD US CLB BACK TO FL230. THE CTLR OBVIOUSLY WAS CAUGHT OFF GUARD BY TWO CONVERGING ACFT AT THE SAME ALT. MAYBE AN ALARM WENT OFF. PROBABLY ONE REASON HE WAS DIFFICULT TO UNDERSTAND IS THAT HE WAS SO EXCITED. HE OBVIOUSLY WAITED TOO LATE TO CONTACT US, BUT IF HE WAS HAVING TROUBLE GETTING US, WHY DIDN'T HE TELL THE OTHER ACFT TO DSND? WHEN THE CTLR HAD FIRST TRIED TO CONTACT US, I WAS JUST SITTING THERE MONITORING THE ACFT. BUT PERHAPS IF I HAD BEEN MORE ALERT, I WOULD HAVE CAUGHT HIS FIRST XMISSION. BUT ALERTNESS IS HARD TO ACHIEVE AFTER BEING ON DUTY THE PREVIOUS DAY FOR 15 HRS AND FLYING OVER 8 HRS IN BAD WX. WITH ONLY AN 8 HR OVERNIGHT AND INTO. OUR 8TH HR OF DUTY ON THIS DAY, EVEN STAYING AWAKE CAN BE A CHALLENGE.
Data retrieved from NASA's ASRS site as of July 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.