 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Air carrier aircraft did not contact radar controller as quickly as anticipated which resulted in less than standard separation. Controller attempted to get aircraft on frequency, but aircraft did not check in. Vectors were issued to provide greater distance between aircraft.
| Attributes | |
| ACN | 332768 |
| Time | |
| Date | 199604 |
| Day | Tue |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | atc facility : cgt |
| State Reference | IL |
| Altitude | msl bound lower : 31000 msl bound upper : 31000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : zau |
| Operator | common carrier : air carrier |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Operating Under FAR Part | Part 121 |
| Flight Phase | cruise other |
| Route In Use | enroute : on vectors |
| Flight Plan | IFR |
| Aircraft 2 | |
| Operator | common carrier : air carrier |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Operating Under FAR Part | Part 121 |
| Flight Phase | cruise other |
| Route In Use | enroute : on vectors |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Qualification | controller : radar |
| Experience | controller military : 4 controller radar : 12 |
| ASRS Report | 332768 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Events | |
| Anomaly | conflict : airborne less severe non adherence : published procedure non adherence : required legal separation |
| Independent Detector | atc equipment other atc equipment : unspecified other controllera |
| Resolutory Action | controller : issued new clearance other |
| Consequence | Other |
| Miss Distance | horizontal : 28200 vertical : 400 |
| Supplementary | |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Operational Error |
Narrative:
Recognized conflict in timely manner. Requested control for turns on aircraft a to turn behind aircraft B. Aircraft a did not check on frequency. 3 mins go by before I asked the controller of aircraft a to put said aircraft on my frequency. I turned aircraft a to a 265 degree heading then 250 degrees, then 230 degrees -- problem was winds caused aircraft a to gain speed (approximately 60-80 KTS). Normally these headings would have been more than enough to provide standard separation, but because of the strong winds and aircraft a not establishing radio communication with me, separation was apparently less than required. Apparently aircraft a was put on my frequency but aircraft a never called until I called him, asking to see if he was sitting on the frequency.
Original NASA ASRS Text
Title: ACR ACFT DID NOT CONTACT RADAR CTLR AS QUICKLY AS ANTICIPATED WHICH RESULTED IN LTSS. CTLR ATTEMPTED TO GET ACFT ON FREQ, BUT ACFT DID NOT CHK IN. VECTORS WERE ISSUED TO PROVIDE GREATER DISTANCE BTWN ACFT.
Narrative: RECOGNIZED CONFLICT IN TIMELY MANNER. REQUESTED CTL FOR TURNS ON ACFT A TO TURN BEHIND ACFT B. ACFT A DID NOT CHK ON FREQ. 3 MINS GO BY BEFORE I ASKED THE CTLR OF ACFT A TO PUT SAID ACFT ON MY FREQ. I TURNED ACFT A TO A 265 DEG HDG THEN 250 DEGS, THEN 230 DEGS -- PROB WAS WINDS CAUSED ACFT A TO GAIN SPD (APPROX 60-80 KTS). NORMALLY THESE HDGS WOULD HAVE BEEN MORE THAN ENOUGH TO PROVIDE STANDARD SEPARATION, BUT BECAUSE OF THE STRONG WINDS AND ACFT A NOT ESTABLISHING RADIO COM WITH ME, SEPARATION WAS APPARENTLY LESS THAN REQUIRED. APPARENTLY ACFT A WAS PUT ON MY FREQ BUT ACFT A NEVER CALLED UNTIL I CALLED HIM, ASKING TO SEE IF HE WAS SITTING ON THE FREQ.
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.