![]() |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
| Attributes | |
| ACN | 126868 |
| Time | |
| Date | 198910 |
| Day | Sat |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | atc facility : hmv |
| State Reference | TN |
| Altitude | msl bound lower : 31400 msl bound upper : 33000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : zid |
| Make Model Name | Small Transport, Low Wing, 2 Turbojet Eng |
| Flight Phase | descent other |
| Route In Use | enroute : direct |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| 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 non radar : 1 controller radar : 19 controller supervisory : 3 |
| ASRS Report | 126868 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : handoff position |
| Qualification | controller : radar |
| Events | |
| Anomaly | conflict : airborne less severe non adherence : required legal separation non adherence : published procedure |
| Independent Detector | atc equipment other atc equipment : unspecified other controllera |
| Resolutory Action | controller : issued new clearance other |
| Consequence | faa : investigated |
| Miss Distance | horizontal : 15680 vertical : 1600 |
| Supplementary | |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Pilot Deviation Operational Error |
Narrative:
The error occurred at the beckley high sector during a heavy traffic period. There were 31 data blocks displayed on the radar scope of which 17 were on frequency--3 leaving the sector, 5 entering and the remainder pointouts. 5 of the aircraft were conflicting at FL330. I discussed the situation with the tracker and we decided to descend small transport X from FL330 to FL310, which would solve most of the conflicts. Aircraft a was at 12 O'clock and 60 mi from small transport X at the time descent clearance was issued. At that time I believed the situation to be resolved. I noticed C/a activated and then deactivated as small transport X started down. I intended to monitor the situation, but was distracted by other aircraft calling on frequency and another traffic situation. I was also offered a break at this time. I believe that it was at this time that C/a reactivated and was suppressed by the tracker west/O my knowledge. When my scan returned to this traffic situation, the aircraft were approximately 7 mi apart and small transport X was only out of FL317. I instructed small transport X to expedite descent and report level at FL310. The report came 5 seconds after aedp activated. I believe the error occurred due to my failure to closely monitor the situation, complicated by distrs elsewhere at the sector and the actions of my tracker--assuming I was aware of the situation and inhibiting the C/a. The fact that it took small transport X 4 mins to descend 2000' also bothers me.
Original NASA ASRS Text
Title: FLT CREW OF SMT X FAILED TO DESCENT IN A TIMELY MANNER. PLT DEVIATION. LESS THAN STANDARD SEPARATION BETWEEN SMT X AND ACFT Y. SYSTEM ERROR.
Narrative: THE ERROR OCCURRED AT THE BECKLEY HIGH SECTOR DURING A HEAVY TFC PERIOD. THERE WERE 31 DATA BLOCKS DISPLAYED ON THE RADAR SCOPE OF WHICH 17 WERE ON FREQ--3 LEAVING THE SECTOR, 5 ENTERING AND THE REMAINDER POINTOUTS. 5 OF THE ACFT WERE CONFLICTING AT FL330. I DISCUSSED THE SITUATION WITH THE TRACKER AND WE DECIDED TO DSND SMT X FROM FL330 TO FL310, WHICH WOULD SOLVE MOST OF THE CONFLICTS. ACFT A WAS AT 12 O'CLOCK AND 60 MI FROM SMT X AT THE TIME DSCNT CLRNC WAS ISSUED. AT THAT TIME I BELIEVED THE SITUATION TO BE RESOLVED. I NOTICED C/A ACTIVATED AND THEN DEACTIVATED AS SMT X STARTED DOWN. I INTENDED TO MONITOR THE SITUATION, BUT WAS DISTRACTED BY OTHER ACFT CALLING ON FREQ AND ANOTHER TFC SITUATION. I WAS ALSO OFFERED A BREAK AT THIS TIME. I BELIEVE THAT IT WAS AT THIS TIME THAT C/A REACTIVATED AND WAS SUPPRESSED BY THE TRACKER W/O MY KNOWLEDGE. WHEN MY SCAN RETURNED TO THIS TFC SITUATION, THE ACFT WERE APPROX 7 MI APART AND SMT X WAS ONLY OUT OF FL317. I INSTRUCTED SMT X TO EXPEDITE DESCENT AND RPT LEVEL AT FL310. THE RPT CAME 5 SECS AFTER AEDP ACTIVATED. I BELIEVE THE ERROR OCCURRED DUE TO MY FAILURE TO CLOSELY MONITOR THE SITUATION, COMPLICATED BY DISTRS ELSEWHERE AT THE SECTOR AND THE ACTIONS OF MY TRACKER--ASSUMING I WAS AWARE OF THE SITUATION AND INHIBITING THE C/A. THE FACT THAT IT TOOK SMT X 4 MINS TO DSND 2000' ALSO BOTHERS ME.
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.