37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 707332 |
Time | |
Date | 200608 |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | navaid : aex.vortac |
State Reference | LA |
Altitude | msl single value : 34000 |
Environment | |
Flight Conditions | Mixed |
Weather Elements | Thunderstorm |
Light | Night |
Aircraft 1 | |
Controlling Facilities | artcc : zme.artcc tower : dfw.tower |
Operator | common carrier : air carrier |
Make Model Name | B737-300 |
Operating Under FAR Part | Part 121 |
Flight Phase | cruise : level |
Flight Plan | IFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : radar |
Qualification | controller : radar |
Experience | controller time certified in position1 : 8 |
ASRS Report | 707332 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Events | |
Anomaly | airspace violation : entry non adherence : required legal separation |
Independent Detector | other controllera |
Resolutory Action | none taken : anomaly accepted |
Consequence | faa : investigated |
Supplementary | |
Problem Areas | Weather Airspace Structure ATC Human Performance |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Operational Deviation |
Narrative:
Several last min WX deviations by several aircraft in the northwest corner of my airspace (ZME sector 45). Some pilots deviated one way then the other. Lots of land line communication between myself and 2 other ZME sectors and 2 ZFW sectors; I could've used some help with a d-side but things happened so fast and staffing was short I don't know that it would've helped. During all of the confusion in the north part of the sector air carrier X crossed ZHU sector 42's boundary without a handoff. I called and effected a verbal and automated handoff. There were no other aircraft anywhere near air carrier X. Last week ZMP was briefed that we had better 'spin' aircraft to avoid airspace violations (deviations). At high altitude this would mean spinning aircraft at least 2 mins from the next boundary. I feel if we did this; especially with most aircraft deviating for WX and no other place to go; it would throw the NAS into a frenzy and burn a lot of the aircraft's fuel unnecessarily.
Original NASA ASRS Text
Title: ZME CTLR EXPERIENCED OPDEV DURING WX DEVS WHEN ACFT ENTERED ZHU'S AIRSPACE WITHOUT A HDOF.
Narrative: SEVERAL LAST MIN WX DEVS BY SEVERAL ACFT IN THE NW CORNER OF MY AIRSPACE (ZME SECTOR 45). SOME PLTS DEVIATED ONE WAY THEN THE OTHER. LOTS OF LAND LINE COM BTWN MYSELF AND 2 OTHER ZME SECTORS AND 2 ZFW SECTORS; I COULD'VE USED SOME HELP WITH A D-SIDE BUT THINGS HAPPENED SO FAST AND STAFFING WAS SHORT I DON'T KNOW THAT IT WOULD'VE HELPED. DURING ALL OF THE CONFUSION IN THE N PART OF THE SECTOR ACR X CROSSED ZHU SECTOR 42'S BOUNDARY WITHOUT A HDOF. I CALLED AND EFFECTED A VERBAL AND AUTOMATED HDOF. THERE WERE NO OTHER ACFT ANYWHERE NEAR ACR X. LAST WEEK ZMP WAS BRIEFED THAT WE HAD BETTER 'SPIN' ACFT TO AVOID AIRSPACE VIOLATIONS (DEVS). AT HIGH ALT THIS WOULD MEAN SPINNING ACFT AT LEAST 2 MINS FROM THE NEXT BOUNDARY. I FEEL IF WE DID THIS; ESPECIALLY WITH MOST ACFT DEVIATING FOR WX AND NO OTHER PLACE TO GO; IT WOULD THROW THE NAS INTO A FRENZY AND BURN A LOT OF THE ACFT'S FUEL UNNECESSARILY.
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.