 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZOB controller experienced operational error at approximately FL160 when assigning aircraft incorrect frequency and receiving controller issued unexpected descent clearance.
| Attributes | |
| ACN | 656444 |
| Time | |
| Date | 200505 |
| Place | |
| Locale Reference | navaid : jxn.vor |
| State Reference | MI |
| Altitude | msl bound lower : 16000 msl bound upper : 17000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : zob.artcc |
| Operator | common carrier : air carrier |
| Make Model Name | Regional Jet CL65 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | descent : approach |
| Flight Plan | IFR |
| Aircraft 2 | |
| Controlling Facilities | artcc : zob.artcc |
| Operator | common carrier : air carrier |
| Make Model Name | DC-9 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | climbout : initial |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Qualification | controller : military |
| Experience | controller military : 9.5 controller time certified in position1 : 1 |
| ASRS Report | 656444 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Qualification | controller : radar |
| Experience | controller limited radar : 3 controller radar : 9 |
| ASRS Report | 656721 |
| Events | |
| Anomaly | conflict : airborne less severe non adherence : required legal separation |
| Independent Detector | atc equipment : conflict alert other controllera other controllerb |
| Resolutory Action | controller : separated traffic controller : issued alert flight crew : took evasive action |
| Miss Distance | horizontal : 18000 vertical : 700 |
| Supplementary | |
| Problem Areas | ATC Human Performance |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Operational Error |
Narrative:
Air carrier X checked onto my frequency descending out of FL185 for 17000 ft. His route of flight runs him from south to north through my airspace and eventually landing at flint; mi. My sector is a detroit departure sector; so my plan was to keep air carrier X at 17000 ft and stop my departures at 16000 ft until they pass. I handed off the air carrier X using the automated handoff to the next sector in my center. After the handoff was accepted; I reiterated for air carrier X to maintain 17000 ft and to expect lower from the next sector. I then switched air carrier X to the wrong frequency. I inadvertently put him onto lansing approach control (126.65) instead of lansing sector (126.75). When air carrier X checked onto lansing approach level at 17000 ft; the approach controller descended him for flint. He started his descent through air carrier Y's altitude; at which point I turned air carrier Y to an immediate 180 degree heading. The approach controller didn't have the handoff; and should have called the center prior to issuing any control instructions to air carrier X.
Original NASA ASRS Text
Title: ZOB CTLR EXPERIENCED OPERROR AT APPROX FL160 WHEN ASSIGNING ACFT INCORRECT FREQ AND RECEIVING CTLR ISSUED UNEXPECTED DSCNT CLRNC.
Narrative: ACR X CHKED ONTO MY FREQ DSNDING OUT OF FL185 FOR 17000 FT. HIS RTE OF FLT RUNS HIM FROM S TO N THROUGH MY AIRSPACE AND EVENTUALLY LNDG AT FLINT; MI. MY SECTOR IS A DETROIT DEP SECTOR; SO MY PLAN WAS TO KEEP ACR X AT 17000 FT AND STOP MY DEPS AT 16000 FT UNTIL THEY PASS. I HANDED OFF THE ACR X USING THE AUTOMATED HDOF TO THE NEXT SECTOR IN MY CTR. AFTER THE HDOF WAS ACCEPTED; I REITERATED FOR ACR X TO MAINTAIN 17000 FT AND TO EXPECT LOWER FROM THE NEXT SECTOR. I THEN SWITCHED ACR X TO THE WRONG FREQ. I INADVERTENTLY PUT HIM ONTO LANSING APCH CTL (126.65) INSTEAD OF LANSING SECTOR (126.75). WHEN ACR X CHKED ONTO LANSING APCH LEVEL AT 17000 FT; THE APCH CTLR DSNDED HIM FOR FLINT. HE STARTED HIS DSCNT THROUGH ACR Y'S ALT; AT WHICH POINT I TURNED ACR Y TO AN IMMEDIATE 180 DEG HDG. THE APCH CTLR DIDN'T HAVE THE HDOF; AND SHOULD HAVE CALLED THE CTR PRIOR TO ISSUING ANY CTL INSTRUCTIONS TO ACR X.
Data retrieved from NASA's ASRS site as of January 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.