 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Btr controllers report of an aircraft being too high for the approach. The pilot requested a 360 turn to get lower. This was approved by developmental; then corrected by him to fly runway heading. The aircraft making missed approach now becomes a conflict with another aircraft. Controllers' report of having an ARTS failure during this operation.
| Attributes | |
| ACN | 1316323 |
| Time | |
| Date | 201512 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | BTR.Tower |
| State Reference | LA |
| Aircraft 1 | |
| Make Model Name | Small Aircraft Low Wing 2 Eng Retractable Gear |
| Flight Phase | Final Approach |
| Route In Use | Visual Approach |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Medium Transport Low Wing 2 Turbojet Eng |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Final Approach |
| Route In Use | Visual Approach |
| Flight Plan | IFR |
| Person 1 | |
| Function | Instructor Local |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 26 |
| Person 2 | |
| Function | Approach |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 6 |
| Events | |
| Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
While giving OJT on local control; we experienced an ARTS malfunction. We had primary and secondary radar but not associated ARTS tags. Radar handed off aircraft X; on a visual approach to runway 13 following aircraft Z. Shortly after radar handed off aircraft Y; following aircraft X on a visual approach. Aircraft X advised that he needed a 360 because he was too high. While I was explaining that due to traffic following we could not issue the 360 to the pilot; the developmental approved the request but went back and told the pilot of aircraft X correction. I told the pilot to fly runway heading and climb to 3;000 which is the standard missed approach/go around procedure at btr. The pilot of aircraft X continued in a climbing right turn instead of runway heading of 130. Aircraft Y had a TCAS RA and turned and climbed to avoid the traffic. The developmental saw the conflict visually and started issuing traffic to both aircraft.
Original NASA ASRS Text
Title: BTR Controllers report of an aircraft being too high for the approach. The pilot requested a 360 turn to get lower. This was approved by Developmental; then corrected by him to fly runway heading. The aircraft making missed approach now becomes a conflict with another aircraft. Controllers' report of having an ARTS failure during this operation.
Narrative: While giving OJT on Local Control; we experienced an ARTS malfunction. We had primary and secondary radar but not associated ARTS tags. Radar handed off Aircraft X; on a visual approach to Runway 13 following Aircraft Z. Shortly after Radar handed off Aircraft Y; following Aircraft X on a visual approach. Aircraft X advised that he needed a 360 because he was too high. While I was explaining that due to traffic following we could not issue the 360 to the pilot; the Developmental approved the request but went back and told the pilot of Aircraft X correction. I told the pilot to fly runway heading and climb to 3;000 which is the standard missed approach/go around procedure at BTR. The pilot of Aircraft X continued in a climbing right turn instead of runway heading of 130. Aircraft Y had a TCAS RA and turned and climbed to avoid the traffic. The Developmental saw the conflict visually and started issuing traffic to both aircraft.
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.