37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1476384 |
Time | |
Date | 201708 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | SAN.Airport |
State Reference | CA |
Aircraft 1 | |
Make Model Name | B737 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | B737 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Route In Use | SID PADRZ1 |
Flight Plan | IFR |
Person 1 | |
Function | Local |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 7 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types Inflight Event / Encounter CFTT / CFIT |
Narrative:
Aircraft X was on a high 2 mile to a mile and a half final. Aircraft X broke out of the clouds at 1700 ft. At that point I realized that aircraft X was not going to make the descent and sent aircraft X around; and I issued aircraft X a 275 heading and to climb to 2500 feet. Prior to me issuing the go around; aircraft Y was on departure roll and on a diverging course (padrz departure). In my opinion the distance between aircraft X and aircraft Y was no factor for each other. As aircraft X started their climb; aircraft Y increased their speed and they over took aircraft X. When I noticed the overtake; I had aircraft Y stop their climb at 1500 feet to provided positive separation until aircraft Y was established on their SID and diverging. Once divergence was established; I instructed aircraft Y to continue their climb to 15000 and switched both aircraft to departure control. By me stopping the climb of aircraft Y at 1500 feet; aircraft Y was below the MVA for the area he was in which is 1900ft. When I first noticed aircraft X was not going to make the approach; I should of turned aircraft X to a 250 heading coordinated with the adjacent airport (nzy) and established diverging course further out and much sooner.
Original NASA ASRS Text
Title: SAN Tower Controller reported sending an aircraft around; which then caused the controller to stop a departure below the Minimum Vectoring Altitude to maintain separation between the two aircraft.
Narrative: Aircraft X was on a high 2 mile to a mile and a half final. Aircraft X broke out of the clouds at 1700 ft. At that point I realized that Aircraft X was not going to make the descent and sent Aircraft X around; and I issued Aircraft X a 275 heading and to climb to 2500 feet. Prior to me issuing the go around; Aircraft Y was on departure roll and on a diverging course (PADRZ departure). In my opinion the distance between Aircraft X and Aircraft Y was no factor for each other. As Aircraft X started their climb; Aircraft Y increased their speed and they over took Aircraft X. When I noticed the overtake; I had Aircraft Y stop their climb at 1500 feet to provided positive separation until Aircraft Y was established on their SID and diverging. Once divergence was established; I instructed Aircraft Y to continue their climb to 15000 and switched both aircraft to departure control. By me stopping the climb of Aircraft Y at 1500 feet; Aircraft Y was below the MVA for the area he was in which is 1900ft. When I first noticed Aircraft X was not going to make the approach; I should of turned Aircraft X to a 250 heading coordinated with the adjacent airport (NZY) and established diverging course further out and much sooner.
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.