37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1005532 |
Time | |
Date | 201204 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | SFO.Airport |
State Reference | CA |
Aircraft 1 | |
Make Model Name | Regional Jet CL65 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Landing |
Route In Use | Visual Approach |
Flight Plan | IFR |
Person 1 | |
Function | Local |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
Sfo was in a 28/28 shoreline configuration. The winds were calm to light so aircraft were coming in staggered and fast. It was a busy departure and arrival hour. Normally with these winds we would be departing the 1's; however due to taxiway closures we were departing the 28's. I was working local control ready to depart off runway 28R with traffic on a few mile final for that runway; when I noticed a crj going missed approach for runway 28L. When queried; the crj said they never received a landing clearance. I told them to fly heading 265; then cleared the departure on runway 28R for take off who would be departing on a west on a 280 heading. I told the crj to maintain 3100. The controller in charge said they thought they heard him read back 2100; but my local assist said they heard 31. Instead of telling the crj to contact norcal departure on 135.1; I said to contact norcal departure. Unfortunately; the crj stopped at 21; and went to the wrong frequency; with the crj going around; it through me off. I should have ensured the proper altitude and given the appropriate departure frequency. I did hold the rest of the aircraft until everything was straightened out; but should have taken more time ensuring everything with the crj. I should also add that frequency congestion could have been a contributing factor.
Original NASA ASRS Text
Title: SFO Controller described a below-MVA event when traffic on final for Runway 28L initiated a go around absent a landing clearing with traffic departing Runway 28R; the reporter assigning the wrong altitude/frequency to missed approach aircraft.
Narrative: SFO was in a 28/28 shoreline configuration. The winds were calm to light so aircraft were coming in staggered and fast. It was a busy departure and arrival hour. Normally with these winds we would be departing the 1's; however due to taxiway closures we were departing the 28's. I was working Local Control ready to depart off Runway 28R with traffic on a few mile final for that runway; when I noticed a CRJ going missed approach for Runway 28L. When queried; the CRJ said they never received a landing clearance. I told them to fly heading 265; then cleared the departure on Runway 28R for take off who would be departing on a west on a 280 heading. I told the CRJ to maintain 3100. The CIC said they thought they heard him read back 2100; but my Local Assist said they heard 31. Instead of telling the CRJ to contact Norcal Departure on 135.1; I said to contact Norcal Departure. Unfortunately; the CRJ stopped at 21; and went to the wrong frequency; with the CRJ going around; it through me off. I should have ensured the proper altitude and given the appropriate departure frequency. I did hold the rest of the aircraft until everything was straightened out; but should have taken more time ensuring everything with the CRJ. I should also add that frequency congestion could have been a contributing factor.
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.