![]() |
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
![]()
There were two rationales given in this thread, and both of them make
sense to me... but which one would you say is more correct? a) stay to the right to make it easier to see the traffic (sitting in the left seat), b) stay to the right to stay away from the pattern (and away from the departing plane's presumed crosswind turn). The reason for asking, of course, is what should you do if the pattern is RH - sidestep to the left or right? I've only had to go around for traffic once and it was a weird situation. I was cleared for T&G on 31. 28 starts to the right of 31, intersects it, and obviously continues to the left. I was on short final when tower cleared someone for takeoff on 28; he started rolling. Since i wanted no part of playing chicken at the intersection, I immediately went around (then announced it), flew the centerline and probably the tower gave me right traffic to stay away from the departure end of 28. The other guy's takeoff clearance was not canceled, and he departed. At the time (pre-solo), I was a little rattled, the tower said "sorry about that" and my instructor said I did the right thing. But, after reading this thread, it made me think about it some more, and I realize I likely did not keep the traffic in sight and in fact may have passed directly over him at some point (certainly a possibility even if it didn't actually happen that way). So, now I think perhaps I should have done something differently, but what? Not crossing 28 would be difficult at best (the airport is KAGC if anyone wants to look at a diagram) - for one, it's going to involve really low altitude turns - no way you're missing the approach end by turning right, and if you go left you're headed towards the hangars and tower. You're also not going to have a lot of choice about your airspeed during the initial stages of the go-around. So what to do? I know now that a 172 should easily be able to land and stop before the intersection, but even now (a whopping ~25 hours later) I wouldn't be entirely comfortable with that... todd |
#2
|
|||
|
|||
![]()
The microphone is not a flight control. It's not what you say that counts,
it's what you do. "Buzzbomb 34X going around, moving to the right of the runway" would be plenty. The rationale for moving to the right is that with you in the left seat, you can watch the other plane and take evasive action if necessary. We have grass between the two parallel runways at Boeing Field in Seattle, and when the tower issues a go-around it is usually "go around, fly over the grass, maintain visual separation from the Flybird to your (right.left), report midfield downwind." Bob Gardner "Nik" wrote in message ups.com... Ok thank you... How would you say the intentions though? -Nik |
#3
|
|||
|
|||
![]()
How would you say the intentions though?
"Too close for missiles...switching to guns." ;-) -- Jay Honeck Iowa City, IA Pathfinder N56993 www.AlexisParkInn.com "Your Aviation Destination" |
#4
|
|||
|
|||
![]()
In article 9hyGf.763279$_o.354991@attbi_s71,
"Jay Honeck" wrote: How would you say the intentions though? "Too close for missiles...switching to guns." I had that happen to me one day I was #3 in a 3-ship returning. #2 went around to clear #1, while an Apache was waiting in the runup area. Just as I was about to turn short base-to-final, the Apache took the runway. I radioed, "Apache, what are you doing?" Apache: "Taking off." I was tempted to slip down and stick my wingtip in his lap but put discretion ahead of valor. As I cleaned up and slid to the right of the runway, I noticed that, not only had the Apache pilot taken the runway without making sure of clear traffic, but he apparently had full flaps and an open door. Somehow, he managed to close the door on the takeoff roll and gain flight. I later talked to the owner, who said that there apparently was a rogue instructor who was selling lessons in the plane without permission. looking back, I am glad I DIDN'T stick my wingtip in his lap, because he apparently had his hands full enough already. |
#5
|
|||
|
|||
![]()
ORVAL FAIRAIRN wrote:
In article 9hyGf.763279$_o.354991@attbi_s71, "Jay Honeck" wrote: How would you say the intentions though? "Too close for missiles...switching to guns." I had that happen to me one day I was #3 in a 3-ship returning. #2 went around to clear #1, while an Apache was waiting in the runup area. Just as I was about to turn short base-to-final, the Apache took the runway. I radioed, "Apache, what are you doing?" Apache: "Taking off." I was tempted to slip down and stick my wingtip in his lap but put discretion ahead of valor. Do you fly a RV? Ron Lee |
#6
|
|||
|
|||
![]() "Kyle Boatright" wrote in message . .. In both cases, announce your intentions, offset your approach and fly an upwind leg (typically to the right of the runway centerline). You should adjust your upwind leg to keep the rogue aircraft/pilot in view until it is no longer a collision threat. At a controlled field, unless told otherwise, you should overfly the runway while climbing to traffic pattern altitude. |
#7
|
|||
|
|||
![]()
Sorry, I don't fly over the same runway when another aircraft could be
right below me, or that I could run into it. ATC would be quite okay with you sidestepping. That is, of course, if you didn't already receive instructions telling you to get out of the way. At a non-towered field, see the above, but announce intentions. If I lose sight of the other traffic, it's no longer "See and Avoid". It becomes, "I made a bad decision and hope the other plane avoids me." Chris G. Steven P. McNicoll wrote: "Kyle Boatright" wrote in message . .. In both cases, announce your intentions, offset your approach and fly an upwind leg (typically to the right of the runway centerline). You should adjust your upwind leg to keep the rogue aircraft/pilot in view until it is no longer a collision threat. At a controlled field, unless told otherwise, you should overfly the runway while climbing to traffic pattern altitude. |
#8
|
|||
|
|||
![]() "Chris G." wrote in message reenews.net... Sorry, I don't fly over the same runway when another aircraft could be right below me, or that I could run into it. ATC would be quite okay with you sidestepping. That is, of course, if you didn't already receive instructions telling you to get out of the way. The instruction, "go around", by itself, means overfly the runway while climbing to traffic pattern altitude. You're not complying with the instruction if you sidestep to the right without being told to do so. |
#9
|
|||
|
|||
![]()
On Wed, 08 Feb 2006 19:11:41 GMT, "Steven P. McNicoll"
wrote: "Chris G." wrote in message freenews.net... Sorry, I don't fly over the same runway when another aircraft could be right below me, or that I could run into it. ATC would be quite okay with you sidestepping. That is, of course, if you didn't already receive instructions telling you to get out of the way. The instruction, "go around", by itself, means overfly the runway while climbing to traffic pattern altitude. You're not complying with the instruction if you sidestep to the right without being told to do so. Maybe so, but the pilot in command is the ultimate authority for the safety of the flight.... For what it's worth, I'd only side-step if I didn't like what I saw below and in front of me. Letting ATC know what I was doing would of course be a polite thing to do! Bela P. Havasreti |
#10
|
|||
|
|||
![]()
Chris G. wrote:
Sorry, I don't fly over the same runway when another aircraft could be right below me, or that I could run into it. ATC would be quite okay with you sidestepping. ATC is usually not ok with you doing something unless they've told you to do it or they know you're going to do it. |
Thread Tools | |
Display Modes | |
|
|