 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Reporter stated he observed aircraft Y deviate from assigned altitude because of RA from aircraft Z; causing separation loss with aircraft X.
| Attributes | |
| ACN | 1158770 |
| Time | |
| Date | 201403 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZOB.ARTCC |
| State Reference | OH |
| Environment | |
| Light | Night |
| Aircraft 1 | |
| Make Model Name | Light Transport |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Medium Large Transport |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 1.5 |
| Events | |
| Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance |
Narrative:
I was working a radar position without a d-side as one was not needed. Aircraft Y was heading southeast; direct cutta intersection at FL350. Aircraft X was heading northwest toward mlp at FL340. The paths of flight of the two aircraft were less than 5 miles apart. Aircraft Y's data block showed FL345 in one hit and the conflict alert initiated. I asked aircraft Y to verify level at FL350. The pilot responded; indicating that they were responding to an RA and descending. After verifying that the RA was to descend and not climb; I noticed another sector had an aircraft; aircraft Z; at FL360 that had shown 100 feet low for a couple hits; causing the RA. The RA resulted in a loss of separation between aircraft Y and aircraft X. Once aircraft Y and aircraft X were laterally separated; I cleared aircraft Y to descend to FL310 once the RA was resolved as the aircraft needed to start it's descent into it's destination airport. Aircraft Z should have been level at FL360. I'm not sure if it was a pilot or equipment error; but the only separation that was lost was with another aircraft not involved in the RA at all.
Original NASA ASRS Text
Title: Reporter stated he observed Aircraft Y deviate from assigned altitude because of RA from Aircraft Z; causing separation loss with Aircraft X.
Narrative: I was working a radar position without a D-side as one was not needed. Aircraft Y was heading southeast; direct CUTTA Intersection at FL350. Aircraft X was heading northwest toward MLP at FL340. The paths of flight of the two aircraft were less than 5 miles apart. Aircraft Y's data block showed FL345 in one hit and the conflict alert initiated. I asked Aircraft Y to verify level at FL350. The pilot responded; indicating that they were responding to an RA and descending. After verifying that the RA was to descend and not climb; I noticed another sector had an aircraft; Aircraft Z; at FL360 that had shown 100 feet low for a couple hits; causing the RA. The RA resulted in a loss of separation between Aircraft Y and Aircraft X. Once Aircraft Y and Aircraft X were laterally separated; I cleared Aircraft Y to descend to FL310 once the RA was resolved as the aircraft needed to start it's descent into it's destination airport. Aircraft Z should have been level at FL360. I'm not sure if it was a pilot or equipment error; but the only separation that was lost was with another aircraft not involved in the RA at all.
Data retrieved from NASA's ASRS site 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.