37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 591847 |
Time | |
Date | 200308 |
Day | Thu |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | navaid : bmi.vor |
State Reference | IL |
Altitude | msl single value : 16000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zau.artcc artcc : zkc.artcc |
Operator | general aviation : personal |
Make Model Name | Citation II S2/Bravo |
Operating Under FAR Part | Part 91 |
Navigation In Use | other |
Flight Phase | cruise : level |
Flight Plan | IFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : radar |
Qualification | controller : radar controller : military |
Experience | controller military : 4 controller radar : 29 controller time certified in position1 : 25 |
ASRS Report | 591847 |
Person 2 | |
Affiliation | government : faa |
Function | controller : radar |
Events | |
Anomaly | airspace violation : entry non adherence : published procedure |
Independent Detector | other controllera |
Resolutory Action | none taken : detected after the fact |
Consequence | faa : investigated |
Supplementary | |
Problem Areas | ATC Human Performance Navigational Facility |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Operational Deviation |
Situations | |
ATC Facility | computer equipment : zau.artcc procedure or policy : zau.artcc |
Narrative:
Departed bmi swbound climbing to 16000 ft. I activated a handoff to ZKC. The handoff was accepted and I xferred radio frequency to ZKC. C550 was landing at a small airport within the springfield approach airspace, and airport I was not familiar with. The handoff went through ZKC to springfield approach. My only indication of this is a one-in-four or one-in-five time share with the airspeed in the data block. Not knowing the airport of landing was in springfield approach airspace, I was not aware of the 'through' handoff nor did I look to see if a 'through' handoff occurred. C550 then got into ZKC's airspace without a proper handoff, violating their airspace. When we had strips, it would show proper coordination, but we now have uret (user requested evaluation tool) and in strips and uret does not show who has the handoff. We have computers that make assumptions that we must be responsible for. Give something I can work with and reason with. Uret is not the answer.
Original NASA ASRS Text
Title: ZAU CTLR DOES NOT OBSERVE RADAR XFER MESSAGE FROM URET (USER REQUESTED EVALUATION TOOL) MISDIRECTED TO SGF APCH CTL WHEN RADAR XFER WAS REQUIRED, AND EXPECTED, TO ZKC.
Narrative: DEPARTED BMI SWBOUND CLBING TO 16000 FT. I ACTIVATED A HDOF TO ZKC. THE HDOF WAS ACCEPTED AND I XFERRED RADIO FREQ TO ZKC. C550 WAS LNDG AT A SMALL ARPT WITHIN THE SPRINGFIELD APCH AIRSPACE, AND ARPT I WAS NOT FAMILIAR WITH. THE HDOF WENT THROUGH ZKC TO SPRINGFIELD APCH. MY ONLY INDICATION OF THIS IS A ONE-IN-FOUR OR ONE-IN-FIVE TIME SHARE WITH THE AIRSPD IN THE DATA BLOCK. NOT KNOWING THE ARPT OF LNDG WAS IN SPRINGFIELD APCH AIRSPACE, I WAS NOT AWARE OF THE 'THROUGH' HDOF NOR DID I LOOK TO SEE IF A 'THROUGH' HDOF OCCURRED. C550 THEN GOT INTO ZKC'S AIRSPACE WITHOUT A PROPER HDOF, VIOLATING THEIR AIRSPACE. WHEN WE HAD STRIPS, IT WOULD SHOW PROPER COORD, BUT WE NOW HAVE URET (USER REQUESTED EVALUATION TOOL) AND IN STRIPS AND URET DOES NOT SHOW WHO HAS THE HDOF. WE HAVE COMPUTERS THAT MAKE ASSUMPTIONS THAT WE MUST BE RESPONSIBLE FOR. GIVE SOMETHING I CAN WORK WITH AND REASON WITH. URET IS NOT THE ANSWER.
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.