 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Sfb controller described a pattern conflict resulting from ATC spacing misjudgments.
| Attributes | |
| ACN | 1025383 |
| Time | |
| Date | 201207 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | SFB.Airport |
| State Reference | FL |
| Aircraft 1 | |
| Make Model Name | SR20 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Final Approach |
| Flight Plan | VFR |
| Aircraft 2 | |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Flight Phase | Final Approach |
| Person 1 | |
| Function | Local |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Conflict Airborne Conflict |
Narrative:
An SR22 was inbound from the south on a modified right base entry; requesting pattern work. Aircraft was at 1;500 ft; was given the instruction to descend to pattern altitude at pilot's discretion; and to enter the right base to runway 09R. Additional traffic was to this aircraft's left; making a base entry to runway 09C for a full stop. Additional traffic was already established in the right traffic pattern of runway 09R. I misjudged the timing of the inbound the SR22 with the other aircraft in the pattern. My plan was to have the SR22 be first to the runway; and the established aircraft follow the SR22. It ended up being a tie; and I tried to correct the situation by having the SR22 fly eastbound (opposite direction of the other aircraft) with the attempts of having the SR22 now follow the other aircraft. I issued traffic to the SR22 after I told him to make the eastbound turn. The pilot did so; and came close to the other aircraft. There are many things: keep the inbound aircraft at 1;500 ft altitude; could have had existing aircraft make a left 360 in the downwind to create more spacing; could have extended the existing aircraft's upwind; could have turned the SR22 westbound; could have had more urgency with the pilot to have him execute his eastbound turn immediately and give a traffic alert to advise him of the reason for the immediate turn.
Original NASA ASRS Text
Title: SFB Controller described a pattern conflict resulting from ATC spacing misjudgments.
Narrative: An SR22 was inbound from the south on a modified right base entry; requesting pattern work. Aircraft was at 1;500 FT; was given the instruction to descend to pattern altitude at pilot's discretion; and to enter the right base to Runway 09R. Additional traffic was to this aircraft's left; making a base entry to Runway 09C for a full stop. Additional traffic was already established in the right traffic pattern of Runway 09R. I misjudged the timing of the inbound the SR22 with the other aircraft in the pattern. My plan was to have the SR22 be first to the runway; and the established aircraft follow the SR22. It ended up being a tie; and I tried to correct the situation by having the SR22 fly eastbound (opposite direction of the other aircraft) with the attempts of having the SR22 now follow the other aircraft. I issued traffic to the SR22 after I told him to make the eastbound turn. The pilot did so; and came close to the other aircraft. There are many things: keep the inbound aircraft at 1;500 FT altitude; could have had existing aircraft make a left 360 in the downwind to create more spacing; could have extended the existing aircraft's upwind; could have turned the SR22 westbound; could have had more urgency with the pilot to have him execute his eastbound turn immediately and give a traffic alert to advise him of the reason for the immediate turn.
Data retrieved from NASA's ASRS site as of July 2013 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.