 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Pct controller reported of a loss of separation resulting from a speed overtake. Controller was also training at the time and attempted to have the developmental fix the situation. Reporter then confronted the transferring controller who said it was not his fault and that the aircraft were separated when he shipped them.
| Attributes | |
| ACN | 1329528 |
| Time | |
| Date | 201602 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | PCT.TRACON |
| State Reference | VA |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Large Transport Low Wing 2 Turbojet Eng |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Climb |
| Route In Use | Vectors SID TERPZ 6 |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Large Transport Low Wing 2 Turbojet Eng |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Climb |
| Route In Use | SID TERPZ 6 |
| Flight Plan | IFR |
| Person 1 | |
| Function | Departure Instructor |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 13 |
| Events | |
| Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Speed All Types |
Narrative:
The wooly sector of the chesapeake (chp) area of pct handed off a number of terpz departures to the fluky sector. Aircraft X was leading/ahead of aircraft Y on the terpz departure. Initial separation when fluky accepted the hand off was about 8 miles with aircraft Y about 10 kts faster. When aircraft Y got to 170 MSL; still in wooly's airspace; the overtake of aircraft Y on aircraft X was around 80 kts with minimal separation longitudinally. I instructed my trainee to turn aircraft X westbound and increase to maximum forward speed and to then turn aircraft Y southbound on a 210 heading. I'm not sure if separation was lost. I am sure after confronting the wooly controller in the breakroom about the overtake situation; he said he was not at fault; that the aircraft were 'separated when I shipped them' and that he no longer had any responsibility for the above mentioned aircraft. He was adamant that he did nothing wrong; and was rather smug in response to my questioning his action or inaction.I'm close to retiring and I'll admit it's been a while since I've sat down and read the .65; but I'm pretty sure a transferring controller is required to resolve all and any conflicts before an aircraft leaves his or her airspace. If this requirement has changed and no longer in effect please disregard this report. However; in my opinion; this action by the controller borders on negligence. My recommendation is that the controller and others like him; understand that all conflicts between aircraft need to be resolved before they leave your sector. Coordinate; amend an altitude; give a speed or a vector; anything to make sure we have separation. To smugly say you did your job and that you; in effect; are not concerned about a potential conflict; is not the FAA I grew up in. He might as well told me to 'go eat s#@%; it's your problem'. That's pretty much what I deciphered from his comment.
Original NASA ASRS Text
Title: PCT Controller reported of a loss of separation resulting from a speed overtake. Controller was also training at the time and attempted to have the Developmental fix the situation. Reporter then confronted the transferring Controller who said it was not his fault and that the aircraft were separated when he shipped them.
Narrative: The Wooly sector of the Chesapeake (CHP) area of PCT handed off a number of TERPZ departures to the Fluky sector. Aircraft X was leading/ahead of Aircraft Y on the TERPZ departure. Initial separation when Fluky accepted the hand off was about 8 miles with Aircraft Y about 10 kts faster. When Aircraft Y got to 170 MSL; still in WOOLY's airspace; the overtake of Aircraft Y on Aircraft X was around 80 kts with minimal separation longitudinally. I instructed my trainee to turn Aircraft X westbound and increase to maximum forward speed and to then turn Aircraft Y southbound on a 210 heading. I'm not sure if separation was lost. I am sure after confronting the WOOLY controller in the breakroom about the overtake situation; he said he was not at fault; that the aircraft were 'separated when I shipped them' and that he no longer had any responsibility for the above mentioned aircraft. He was adamant that he did nothing wrong; and was rather smug in response to my questioning his action or inaction.I'm close to retiring and I'll admit it's been a while since I've sat down and read the .65; but I'm pretty sure a transferring controller is required to resolve all and any conflicts before an aircraft leaves his or her airspace. If this requirement has changed and no longer in effect please disregard this report. However; in my opinion; this action by the controller borders on negligence. My recommendation is that the controller and others like him; understand that all conflicts between aircraft need to be resolved before they leave your sector. Coordinate; amend an altitude; give a speed or a vector; anything to make sure we have separation. To smugly say you did your job and that you; in effect; are not concerned about a potential conflict; is not the FAA I grew up in. He might as well told me to 'go eat s#@%; it's your problem'. That's pretty much what I deciphered from his comment.
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.