37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 422549 |
Time | |
Date | 199812 |
Day | Fri |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | atc facility : zmp airport : apn |
State Reference | MN |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : sea |
Operator | common carrier : air carrier |
Make Model Name | SF 340A |
Navigation In Use | Other |
Flight Phase | descent other |
Route In Use | approach : visual |
Flight Plan | IFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : radar |
Experience | controller military : 9 controller radar : 28 |
ASRS Report | 422549 |
Person 2 | |
Affiliation | government : faa |
Function | controller : radar |
Events | |
Anomaly | non adherence : published procedure other anomaly other |
Independent Detector | other controllera |
Resolutory Action | other |
Consequence | Other |
Supplementary | |
Air Traffic Incident | Operational Deviation |
Narrative:
I received a position relief briefing and assumed control of the sector at XA34. Flint low sector apreqed aircraft X off dtw direct apn at 13000 ft. Aircraft X checked on frequency and several mins later asked for lower. I assigned descent to 5800 ft. Aircraft X reported alpena, mi, airport in sight, was issued a visual approach, and changed to airport advisory frequency. About 2 mins later alpena approach called on the voice page line and asked if I had any aircraft in their area. I told them I forgot they were open and immediately gave them the information on aircraft X. I did not in fact remember the mention of alpena approach during my relief briefing when assuming control of the sector. At the time of the incident, I believed that alpena approach was closed. I believe the main contributing factor to this incident is the irregular hours of operation by this part time approach control. The second contributing factor was lack of use of relief briefing checklist in a challenge/response format. The checklist items were covered but in a rapid-fire fashion and my mind was busy digesting a previous checklist item when mention of 'alpena approach is open' was made, so I didn't 'hear' it. The approach control airspace was not 'tagged' on the radar scope with a CST data block.
Original NASA ASRS Text
Title: DURING RELIEF BRIEFING ARTCC RELIEVING AT ZMP DID NOT HEAR THE RELIEVED CTLR TELL HIM THAT ALPENA APCH CTL WAS IN OP. THIS RESULTED IN THE ARTCC CTLR CLRING AN ACFT FOR A VISUAL APCH TO ALPENA ARPT RESULTING IN AN OPDEV.
Narrative: I RECEIVED A POS RELIEF BRIEFING AND ASSUMED CTL OF THE SECTOR AT XA34. FLINT LOW SECTOR APREQED ACFT X OFF DTW DIRECT APN AT 13000 FT. ACFT X CHKED ON FREQ AND SEVERAL MINS LATER ASKED FOR LOWER. I ASSIGNED DSCNT TO 5800 FT. ACFT X RPTED ALPENA, MI, ARPT IN SIGHT, WAS ISSUED A VISUAL APCH, AND CHANGED TO ARPT ADVISORY FREQ. ABOUT 2 MINS LATER ALPENA APCH CALLED ON THE VOICE PAGE LINE AND ASKED IF I HAD ANY ACFT IN THEIR AREA. I TOLD THEM I FORGOT THEY WERE OPEN AND IMMEDIATELY GAVE THEM THE INFO ON ACFT X. I DID NOT IN FACT REMEMBER THE MENTION OF ALPENA APCH DURING MY RELIEF BRIEFING WHEN ASSUMING CTL OF THE SECTOR. AT THE TIME OF THE INCIDENT, I BELIEVED THAT ALPENA APCH WAS CLOSED. I BELIEVE THE MAIN CONTRIBUTING FACTOR TO THIS INCIDENT IS THE IRREGULAR HRS OF OP BY THIS PART TIME APCH CTL. THE SECOND CONTRIBUTING FACTOR WAS LACK OF USE OF RELIEF BRIEFING CHKLIST IN A CHALLENGE/RESPONSE FORMAT. THE CHKLIST ITEMS WERE COVERED BUT IN A RAPID-FIRE FASHION AND MY MIND WAS BUSY DIGESTING A PREVIOUS CHKLIST ITEM WHEN MENTION OF 'ALPENA APCH IS OPEN' WAS MADE, SO I DIDN'T 'HEAR' IT. THE APCH CTL AIRSPACE WAS NOT 'TAGGED' ON THE RADAR SCOPE WITH A CST DATA BLOCK.
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.