 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Nct TRACON controller experienced operational error at FL230; alleging facility flash through procedure and slow climbing air carrier as contributory.
| Attributes | |
| ACN | 790994 |
| Time | |
| Date | 200805 |
| Place | |
| Locale Reference | navaid : lin.vortac |
| State Reference | CA |
| Altitude | msl single value : 23000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : nct.tracon |
| Operator | general aviation : personal |
| Make Model Name | Learjet 60 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | cruise : level |
| Flight Plan | IFR |
| Aircraft 2 | |
| Controlling Facilities | tracon : nct.tracon |
| Operator | common carrier : air carrier |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | climbout : takeoff |
| Route In Use | departure sid : lin9 |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : approach |
| Qualification | controller : radar controller : developmental controller : military |
| Experience | controller military : 6 controller radar : 1 controller time certified in position1 : 5 |
| ASRS Report | 790994 |
| Events | |
| Anomaly | conflict : airborne critical non adherence : required legal separation |
| Independent Detector | other controllera |
| Resolutory Action | controller : issued new clearance |
| Consequence | faa : investigated |
| Miss Distance | horizontal : 8700 vertical : 500 |
| Supplementary | |
| Problem Areas | ATC Human Performance |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Operational Error |
Narrative:
Accepted handoff on aircraft X LJ60. He checked on level at FL230. Aircraft Y; B737; was a flash through (per the SOP via SID); he was not on my frequency. When I noticed the conflict between aircraft X and aircraft Y; I immediately took measures to ensure separation was maintained. I did this by immediately descending aircraft X to FL220. Aircraft X responded that he had traffic in sight. I instructed him to continue descending to FL220. The collision alert never went off and aircraft Y slowed his climb due to gas prices. Had the collision alert gone off; I might have noticed it sooner. This flash-through procedure has been a problem waiting to happen for a long time. The procedure needs to be changed.
Original NASA ASRS Text
Title: NCT TRACON CTLR EXPERIENCED OPERROR AT FL230; ALLEGING FACILITY FLASH THROUGH PROC AND SLOW CLIMBING ACR AS CONTRIBUTORY.
Narrative: ACCEPTED HDOF ON ACFT X LJ60. HE CHKED ON LEVEL AT FL230. ACFT Y; B737; WAS A FLASH THROUGH (PER THE SOP VIA SID); HE WAS NOT ON MY FREQ. WHEN I NOTICED THE CONFLICT BTWN ACFT X AND ACFT Y; I IMMEDIATELY TOOK MEASURES TO ENSURE SEPARATION WAS MAINTAINED. I DID THIS BY IMMEDIATELY DSNDING ACFT X TO FL220. ACFT X RESPONDED THAT HE HAD TFC IN SIGHT. I INSTRUCTED HIM TO CONTINUE DSNDING TO FL220. THE COLLISION ALERT NEVER WENT OFF AND ACFT Y SLOWED HIS CLB DUE TO GAS PRICES. HAD THE COLLISION ALERT GONE OFF; I MIGHT HAVE NOTICED IT SOONER. THIS FLASH-THROUGH PROC HAS BEEN A PROB WAITING TO HAPPEN FOR A LONG TIME. THE PROC NEEDS TO BE CHANGED.
Data retrieved from NASA's ASRS site as of May 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.