 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZME controller experienced operational error at FL350 while providing alternative routings in a WX impacted sector.
| Attributes | |
| ACN | 664873 |
| Time | |
| Date | 200507 |
| Place | |
| Locale Reference | navaid : bna.vortac |
| State Reference | TN |
| Altitude | msl single value : 35000 |
| Environment | |
| Flight Conditions | IMC |
| Weather Elements | Turbulence Thunderstorm |
| Light | Night |
| Aircraft 1 | |
| Controlling Facilities | artcc : zme.artcc |
| Operator | common carrier : air carrier |
| Make Model Name | DC-9 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | cruise : level |
| Flight Plan | IFR |
| Aircraft 2 | |
| Controlling Facilities | artcc : zme.artcc |
| Operator | common carrier : air carrier |
| Make Model Name | Commercial Fixed Wing |
| 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 radar : 15 |
| ASRS Report | 664873 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Events | |
| Anomaly | conflict : airborne less severe non adherence : required legal separation |
| Independent Detector | atc equipment : conflict alert aircraft equipment : tcas |
| Resolutory Action | controller : issued alert controller : issued new clearance flight crew : took evasive action |
| Consequence | faa : investigated |
| Miss Distance | horizontal : 21600 vertical : 600 |
| Supplementary | |
| Problem Areas | ATC Human Performance Weather |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Operational Error |
Narrative:
On the evening I was moderately busy with a lot of WX in my sector and all eastbound aircraft were deviating. The WX covered portions of three sectors in three ctrs and there was much coordination required due to WX. My radar associate was busy with a flight plan input and other coordination. The 2 aircraft got together east of nashville (1 sbound; 1 eastbound). My attention was diverted from the situation developing by the WX impacting the sector. The situation might have benefited greatly if tmu had provided a standard WX rerte to eliminate all the coordination. No such routing was provided.
Original NASA ASRS Text
Title: ZME CTLR EXPERIENCED OPERROR AT FL350 WHILE PROVIDING ALTERNATIVE ROUTINGS IN A WX IMPACTED SECTOR.
Narrative: ON THE EVENING I WAS MODERATELY BUSY WITH A LOT OF WX IN MY SECTOR AND ALL EBOUND ACFT WERE DEVIATING. THE WX COVERED PORTIONS OF THREE SECTORS IN THREE CTRS AND THERE WAS MUCH COORD REQUIRED DUE TO WX. MY RADAR ASSOCIATE WAS BUSY WITH A FLT PLAN INPUT AND OTHER COORD. THE 2 ACFT GOT TOGETHER E OF NASHVILLE (1 SBOUND; 1 EBOUND). MY ATTN WAS DIVERTED FROM THE SIT DEVELOPING BY THE WX IMPACTING THE SECTOR. THE SIT MIGHT HAVE BENEFITED GREATLY IF TMU HAD PROVIDED A STANDARD WX RERTE TO ELIMINATE ALL THE COORD. NO SUCH ROUTING WAS PROVIDED.
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.