 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ARTCC radar controller did not observe a potential conflict less than standard separation situation developing between 2 air carrier aircraft inbound to cle until it was too late to correct. Aircraft were being handed off to approach control at the time that less than standard separation occurred. Controller feels the airspace is not big enough to accommodate arrs from 2 different directions.
| Attributes | |
| ACN | 369410 |
| Time | |
| Date | 199705 |
| Day | Thu |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | atc facility : djb airport : cle |
| State Reference | OH |
| Altitude | msl bound lower : 10000 msl bound upper : 10000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : zob |
| Operator | common carrier : air carrier |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 121 |
| Flight Phase | descent other |
| Route In Use | arrival other |
| Flight Plan | IFR |
| Aircraft 2 | |
| Operator | common carrier : air carrier |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 121 |
| Flight Phase | descent other |
| Route In Use | arrival other |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Qualification | controller : radar |
| Experience | controller radar : 8 |
| ASRS Report | 369410 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : flight data |
| Qualification | controller : radar |
| Events | |
| Anomaly | conflict : airborne less severe non adherence : required legal separation non adherence : published procedure |
| Independent Detector | atc equipment other atc equipment : unspecified other controllera |
| Resolutory Action | none taken : anomaly accepted |
| Consequence | Other |
| Miss Distance | horizontal : 23400 vertical : 0 |
| Supplementary | |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Operational Error |
Narrative:
Aircraft #1 was inbound to cle from over tvt descending to 15000 ft. When I took him from ZID, I cleared him to cross keatn at 10000 ft. This is a nnebound route of flight. Aircraft #2 was inbound to cle from over bsv at 10000 ft. When I first saw the 2 aircraft I checked it and they looked ok. I got busy with some other sits and didn't check again until it was too late to correct. Contributing factors: 1) there is not enough room for the mfd sector radar controller to sequence inbound aircraft to cle when they are coming from over bsv and tvt at the same time. It is approximately 25 mi from the ZID/ZOB boundary to keatn and approximately 10 mi from the bsv/mfd sector boundaries to keatn. Unless the bsv controller sees these sits in advance and starts something early, then it is a scramble every time. Solution: eliminate the inbound route to cle from over the bsv VOR for jet aircraft. 2) I did not have the 5 mi vector line available. 3) my radar associate was not able to hear my coordination because of new equipment. He stated he heard something about speeds and assumed it was for those 2 aircraft.
Original NASA ASRS Text
Title: ARTCC RADAR CTLR DID NOT OBSERVE A POTENTIAL CONFLICT LTSS SIT DEVELOPING BTWN 2 ACR ACFT INBOUND TO CLE UNTIL IT WAS TOO LATE TO CORRECT. ACFT WERE BEING HANDED OFF TO APCH CTL AT THE TIME THAT LTSS OCCURRED. CTLR FEELS THE AIRSPACE IS NOT BIG ENOUGH TO ACCOMMODATE ARRS FROM 2 DIFFERENT DIRECTIONS.
Narrative: ACFT #1 WAS INBOUND TO CLE FROM OVER TVT DSNDING TO 15000 FT. WHEN I TOOK HIM FROM ZID, I CLRED HIM TO CROSS KEATN AT 10000 FT. THIS IS A NNEBOUND RTE OF FLT. ACFT #2 WAS INBOUND TO CLE FROM OVER BSV AT 10000 FT. WHEN I FIRST SAW THE 2 ACFT I CHKED IT AND THEY LOOKED OK. I GOT BUSY WITH SOME OTHER SITS AND DIDN'T CHK AGAIN UNTIL IT WAS TOO LATE TO CORRECT. CONTRIBUTING FACTORS: 1) THERE IS NOT ENOUGH ROOM FOR THE MFD SECTOR RADAR CTLR TO SEQUENCE INBOUND ACFT TO CLE WHEN THEY ARE COMING FROM OVER BSV AND TVT AT THE SAME TIME. IT IS APPROX 25 MI FROM THE ZID/ZOB BOUNDARY TO KEATN AND APPROX 10 MI FROM THE BSV/MFD SECTOR BOUNDARIES TO KEATN. UNLESS THE BSV CTLR SEES THESE SITS IN ADVANCE AND STARTS SOMETHING EARLY, THEN IT IS A SCRAMBLE EVERY TIME. SOLUTION: ELIMINATE THE INBOUND RTE TO CLE FROM OVER THE BSV VOR FOR JET ACFT. 2) I DID NOT HAVE THE 5 MI VECTOR LINE AVAILABLE. 3) MY RADAR ASSOCIATE WAS NOT ABLE TO HEAR MY COORD BECAUSE OF NEW EQUIP. HE STATED HE HEARD SOMETHING ABOUT SPDS AND ASSUMED IT WAS FOR THOSE 2 ACFT.
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.