37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1182016 |
Time | |
Date | 201406 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | ZMA.ARTCC |
State Reference | FL |
Aircraft 1 | |
Make Model Name | Large Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Medium Large Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 25.8 |
Person 2 | |
Function | Other / Unknown |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 9 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Published Material / Policy |
Narrative:
Was working R20 position with a d-side in place. From what I remember (and what OM told me later) that aircraft X checked on the frequency stating he had a clearance 'to cross abeam osogy at FL240.' aircraft Y was climbing to FL230 off pbi airport converging with aircraft X. I called traffic to each. I then noticed that aircraft X was descending below his assigned altitude. I observed his mode C at FL234. I told aircraft X to maintain FL230 which he immediately read back. Then I went back to aircraft Y and issued 'aircraft Y maintain FL220 immediately.' he read it back promptly also. Both aircraft leveled at the newly assigned altitudes. No separation was lost. Aircraft Y reported that the RA was being given at the same time I leveled off the aircraft at FL220.I think the point of osogy should be moved a few miles south or north of where it is to de-conflict with the common blufi departures. Too many times both aircraft are leveling or about to level and there are many ras even after calling traffic to both planes.
Original NASA ASRS Text
Title: Two ZMA controllers describe a near loss of separation.
Narrative: Was working R20 position with a D-side in place. From what I remember (and what OM told me later) that Aircraft X checked on the frequency stating he had a clearance 'to cross abeam OSOGY at FL240.' Aircraft Y was climbing to FL230 off PBI airport converging with Aircraft X. I called traffic to each. I then noticed that Aircraft X was descending below his assigned altitude. I observed his Mode C at FL234. I told Aircraft X to maintain FL230 which he immediately read back. Then I went back to Aircraft Y and issued 'Aircraft Y maintain FL220 immediately.' He read it back promptly also. Both aircraft leveled at the newly assigned altitudes. No separation was lost. Aircraft Y reported that the RA was being given at the same time I leveled off the aircraft at FL220.I think the point of OSOGY should be moved a few miles south or north of where it is to de-conflict with the common BLUFI departures. Too many times both aircraft are leveling or about to level and there are many RAs even after calling traffic to both planes.
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.