37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 896063 |
Time | |
Date | 201006 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZFW.ARTCC |
State Reference | TX |
Aircraft 1 | |
Make Model Name | EMB ERJ 145 ER&LR |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Flight Plan | IFR |
Person 1 | |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy |
Narrative:
Aircraft X; an E145 was holding over sps for delays into dfw at FL330. The airport was not closed but there was a 20 mit (miles in trail) restriction that we could not meet without holding. Aircraft Y was inbound to sps to hold; also at FL330. Conflict alert activated when the aircraft where about 1 1/2 minutes apart. I issued aircraft X a clearance to expedite to FL320; report reaching FL320. He acknowledged. I then issued aircraft Y a turn to a 170 heading and traffic. He acknowledged but did not appear to turn. Neither aircraft responded to an RA. I don't know how many aircraft we where working at the time of the event; the sector was fully staffed with right; RA; and hand-off. Frequency congestion was very bad. The 20 mit restriction; coupled with aircraft coming from other corner posts that had shut due to weather made for an impossible situation. When a sector goes crazy; we need to route aircraft; overflights; around the sector. There needs to be better communication with the pilots; there were a lot of questions about weather; delays; etc. This ties up the frequencies. This particular sector has little airspace and is right next to the sector it is feeding; which can be good for sequencing but leaves no room for the hand-off guy and marginalizes his contributions. Also; when we have expanded in-trail; the ukw sector should not get a stream from sps and a separate stream from adm-hi. It's too much coordination to be down the tubes; have someone pointed out; and have to follow or adjust your stream of aircraft because of it.
Original NASA ASRS Text
Title: ZFW Controller described a loss of separation event when two aircraft entered holding for DFW at the same altitude. The reporter lists weather; frequency congestion and coordination requirements as casual factors.
Narrative: Aircraft X; an E145 was holding over SPS for delays into DFW at FL330. The airport was not closed but there was a 20 MIT (miles in trail) restriction that we could not meet without holding. Aircraft Y was inbound to SPS to hold; also at FL330. Conflict Alert activated when the aircraft where about 1 1/2 minutes apart. I issued Aircraft X a clearance to expedite to FL320; report reaching FL320. He acknowledged. I then issued Aircraft Y a turn to a 170 heading and traffic. He acknowledged but did not appear to turn. Neither aircraft responded to an RA. I don't know how many aircraft we where working at the time of the event; the sector was fully staffed with R; RA; and Hand-Off. Frequency congestion was very bad. The 20 MIT restriction; coupled with aircraft coming from other corner posts that had shut due to weather made for an impossible situation. When a sector goes crazy; we need to route aircraft; overflights; around the sector. There needs to be better communication with the pilots; there were a lot of questions about weather; delays; etc. This ties up the frequencies. This particular sector has little airspace and is right next to the sector it is feeding; which can be good for sequencing but leaves no room for the hand-off guy and marginalizes his contributions. Also; when we have expanded in-trail; the UKW Sector should not get a stream from SPS and a separate stream from ADM-HI. It's too much coordination to be down the tubes; have someone pointed out; and have to follow or adjust your stream of aircraft because of it.
Data retrieved from NASA's ASRS site as of April 2012 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.