37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1174995 |
Time | |
Date | 201405 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | SFO.Airport |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Aircraft Low Wing 1 Eng Retractable Gear |
Operating Under FAR Part | Part 91 |
Flight Phase | Landing |
Route In Use | Visual Approach |
Flight Plan | VFR |
Aircraft 2 | |
Make Model Name | Large Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Route In Use | SID SHORELINE5 |
Flight Plan | IFR |
Person 1 | |
Function | Local |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 17 |
Person 2 | |
Function | Other / Unknown |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 14 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Inflight Event / Encounter Unstabilized Approach |
Narrative:
Aircraft X was vectored on to the runway 28R final approach course for a VFR approach to landing at sfo. I cleared aircraft X to land number 2 behind a regional jet which he reported in sight upon initial contact. The regional jet was approximately 4 to 5 miles ahead of aircraft X. Aircraft X was approximately 10 to 20 knots faster than the regional jet traffic he was following so I advised him to continue to slow as he was gaining on traffic ahead. When aircraft X was approximately 1 mile final I advised him that a long landing was approved and that he could plan to exit the runway at taxiway K. At approximately this same time; I told aircraft Y to 'line up and wait on runway 28L.' I noticed that aircraft X was still airborne at approximately 50 feet or so and slowly descending as he flew down the runway just past the approach end of runway 28R. I then cleared aircraft Y for takeoff on runway 28L. Aircraft Y was a Shoreline5 departure which meant he would turn right crosswind after takeoff. I turned to observe aircraft Y make his right turn and realized aircraft X was climbing and was at about 500 feet on a right crosswind; aircraft Y was outside of and above aircraft X at about 1;200 feet. I asked aircraft X what he was doing to which he replied; 'I started to porpoise on landing so I went around.' I told him that he needs to advise me when he is on a missed approach to which he replied that he had announced it. I never heard any such announcement and after listening to the recording later; there was no such announcement made. I asked him what he wanted to do and he said he wanted to go back to sql so vectored aircraft X downwind towards the san mateo bridge to get him headed towards sql.as soon as the aircraft was under control the pilot of aircraft X should have aggressively let it be known that he was climbing on a missed approach. It was still early morning and the shades were down and the sun was shining bright from the east where aircraft X was operating. These conditions make operations challenging enough and add to that major airport construction and a very small aircraft; extra due diligence is called for. I had no reason to expect nor did I see aircraft X execute a missed approach. Had I observed or been told by the pilot of aircraft X that he was executing a missed approach; alternate instructions could have been given to all aircraft involved.
Original NASA ASRS Text
Title: Pilot reports of porpoising on final and then having to execute a missed approach; while off his left an air carrier departing is turning towards him. Controllers report of pilot not advising the Tower that the aircraft was going around.
Narrative: Aircraft X was vectored on to the Runway 28R final approach course for a VFR approach to landing at SFO. I cleared Aircraft X to land number 2 behind a regional jet which he reported in sight upon initial contact. The regional jet was approximately 4 to 5 miles ahead of Aircraft X. Aircraft X was approximately 10 to 20 knots faster than the regional jet traffic he was following so I advised him to continue to slow as he was gaining on traffic ahead. When Aircraft X was approximately 1 mile final I advised him that a long landing was approved and that he could plan to exit the runway at Taxiway K. At approximately this same time; I told Aircraft Y to 'Line up and wait on Runway 28L.' I noticed that Aircraft X was still airborne at approximately 50 feet or so and slowly descending as he flew down the runway just past the approach end of Runway 28R. I then cleared Aircraft Y for takeoff on Runway 28L. Aircraft Y was a Shoreline5 Departure which meant he would turn right crosswind after takeoff. I turned to observe Aircraft Y make his right turn and realized Aircraft X was climbing and was at about 500 feet on a right crosswind; Aircraft Y was outside of and above Aircraft X at about 1;200 feet. I asked Aircraft X what he was doing to which he replied; 'I started to porpoise on landing so I went around.' I told him that he needs to advise me when he is on a missed approach to which he replied that he had announced it. I never heard any such announcement and after listening to the recording later; there was no such announcement made. I asked him what he wanted to do and he said he wanted to go back to SQL so vectored Aircraft X downwind towards the San Mateo Bridge to get him headed towards SQL.As soon as the aircraft was under control the pilot of Aircraft X should have aggressively let it be known that he was climbing on a missed approach. It was still early morning and the shades were down and the sun was shining bright from the east where Aircraft X was operating. These conditions make operations challenging enough and add to that major airport construction and a very small aircraft; extra due diligence is called for. I had no reason to expect nor did I see Aircraft X execute a missed approach. Had I observed or been told by the pilot of Aircraft X that he was executing a missed approach; alternate instructions could have been given to all aircraft involved.
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.