 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
An SF340 first officer sets up the tower controller for a loss of separation with a potential conflict when he fails to turn onto the downwind leg after a go around. Captain was busy briefing flight attendant about the go around at gsp, sc.
| Attributes | |
| ACN | 458432 |
| Time | |
| Date | 199912 |
| Day | Thu |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : gsp.airport |
| State Reference | SC |
| Altitude | agl single value : 1200 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tower : gsp.tower |
| Operator | common carrier : air carrier |
| Make Model Name | SF 340A |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | other |
| Flight Phase | landing : go around |
| Route In Use | approach : traffic pattern |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp pilot : cfi pilot : instrument pilot : multi engine pilot : commercial |
| Experience | flight time last 90 days : 100 flight time total : 5100 flight time type : 3000 |
| ASRS Report | 458432 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : multi engine pilot : instrument pilot : commercial |
| Events | |
| Anomaly | conflict : airborne less severe non adherence : clearance non adherence : published procedure non adherence : required legal separation other anomaly other other spatial deviation |
| Independent Detector | other controllera |
| Resolutory Action | controller : issued advisory controller : issued new clearance other |
| Consequence | other |
| Supplementary | |
| Problem Areas | Flight Crew Human Performance |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
The first officer was flying. He was new to the company and still on high minimums. His descent into gsp was started late and resulted in a go around because we were too high to land. We cleaned the aircraft up and were instructed to enter downwind. I then informed the flight attendant of our go around. When I was done talking to her on the interphone, the first officer was still on crosswind, never turned downwind and still heading away from the airport. The tower called traffic for us at 12 O'clock, a conflict he wasn't planning on, because had we turned downwind promptly, the traffic would have been in back of us as tower had originally planned after the go around. This conflict upset the controller as we could tell by his voice on the radio. We turned downwind and were handed off to approach and resequenced for another approach. Separation during the incident was adequate 3-4 mi, but nonetheless scared the controller. Lesson learned: before briefing the flight attendant, stabilize the situation (go around), ask if the first officer has got everything under control, then when he is comfortable, go brief the flight attendant. Contributing factors: new first officer, low time, very low time in aircraft. Most likely his first real go around in this aircraft.
Original NASA ASRS Text
Title: AN SF340 FO SETS UP THE TWR CTLR FOR A LOSS OF SEPARATION WITH A POTENTIAL CONFLICT WHEN HE FAILS TO TURN ONTO THE DOWNWIND LEG AFTER A GAR. CAPT WAS BUSY BRIEFING FLT ATTENDANT ABOUT THE GAR AT GSP, SC.
Narrative: THE FO WAS FLYING. HE WAS NEW TO THE COMPANY AND STILL ON HIGH MINIMUMS. HIS DSCNT INTO GSP WAS STARTED LATE AND RESULTED IN A GAR BECAUSE WE WERE TOO HIGH TO LAND. WE CLEANED THE ACFT UP AND WERE INSTRUCTED TO ENTER DOWNWIND. I THEN INFORMED THE FLT ATTENDANT OF OUR GAR. WHEN I WAS DONE TALKING TO HER ON THE INTERPHONE, THE FO WAS STILL ON XWIND, NEVER TURNED DOWNWIND AND STILL HDG AWAY FROM THE ARPT. THE TWR CALLED TFC FOR US AT 12 O'CLOCK, A CONFLICT HE WASN'T PLANNING ON, BECAUSE HAD WE TURNED DOWNWIND PROMPTLY, THE TFC WOULD HAVE BEEN IN BACK OF US AS TWR HAD ORIGINALLY PLANNED AFTER THE GAR. THIS CONFLICT UPSET THE CTLR AS WE COULD TELL BY HIS VOICE ON THE RADIO. WE TURNED DOWNWIND AND WERE HANDED OFF TO APCH AND RESEQUENCED FOR ANOTHER APCH. SEPARATION DURING THE INCIDENT WAS ADEQUATE 3-4 MI, BUT NONETHELESS SCARED THE CTLR. LESSON LEARNED: BEFORE BRIEFING THE FLT ATTENDANT, STABILIZE THE SIT (GAR), ASK IF THE FO HAS GOT EVERYTHING UNDER CTL, THEN WHEN HE IS COMFORTABLE, GO BRIEF THE FLT ATTENDANT. CONTRIBUTING FACTORS: NEW FO, LOW TIME, VERY LOW TIME IN ACFT. MOST LIKELY HIS FIRST REAL GAR IN THIS ACFT.
Data retrieved from NASA's ASRS site as of July 2007 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.