ATC "you're #2 behind an Embraer" but we were cleared on different runways?

Badger

Pattern Altitude
Joined
Dec 29, 2011
Messages
2,136
Display Name

Display name:
Badger
Class C.
ATC let me know I was #2 behind a Embraer, but we were inbound for different for runways...is this a normal ATC call? I thought #2 meant for the same runway. Anyone else with experience like this? (I think ATC actually said follow traffic, but I don't recall the actual verbiage)


The jet was crossing in front of me, I had him in sight and replied with traffic in sight.
 
Class C.
ATC let me know I was #2 behind a Embraer, but we were inbound for different for runways...is this a normal ATC call? I thought #2 meant for the same runway. Anyone else with experience like this? (I think ATC actually said follow traffic, but I don't recall the actual verbiage)


The jet was crossing in front of me, I had him in sight and replied with traffic in sight.

Was the Embraer a Part 121 operation? Do the runways intersect?
 
Was the Embraer a Part 121 operation? Do the runways intersect?

I'm not sure of the part 121 question (does that effect protocol?)
Yes, the runways intersect.
 
Last edited:
The next question is whether you were IFR or not.
 
On my approach Saturday. ATC said you are #2 clear to land runway 18. I responded #1 in sight landing on runway 24. He replied "you are #2 for the intersection. Roger!
 
many 121 operators do not permit LAHSO ops with GA, so if you were #1 for the other runway, then the Embraer would have had to go around for another try. Just trying to keep the separation to the airline ops mins. . . .
 
Our local tower will assign #1 #2 #3 to the runway and will also assign numbers to the airport for th intersecting runways.
 
Sounds like one of those 'workarounds' for 121 that can't participate in LAHSO where there is a potential conflict with traffic on an intersecting runway. Not really #2, but not really #1 either, as the other traffic on the other runway can't LAHSO, or the #2 can LAHSO but the #1 can't allow it. Surely, this isn't well explained, but I've heard it before too at some place in MO, and asked the FBO guy about it, he says he hears it all the time with the 121 guys.
 
Sounds like one of those 'workarounds' for 121 that can't participate in LAHSO where there is a potential conflict with traffic on an intersecting runway. Not really #2, but not really #1 either, as the other traffic on the other runway can't LAHSO, or the #2 can LAHSO but the #1 can't allow it. Surely, this isn't well explained, but I've heard it before too at some place in MO, and asked the FBO guy about it, he says he hears it all the time with the 121 guys.

It's not just that the Part 121 operation can't be issued LAHSO, you can't have LAHSO if a Part 121 operation is involved. For example, even if a Part 121 operation has the full length runway available to it, a Part 91 operation cannot be instructed to land and hold short of an intersecting runway.
 
It's not just that the Part 121 operation can't be issued LAHSO, you can't have LAHSO if a Part 121 operation is involved. For example, even if a Part 121 operation has the full length runway available to it, a Part 91 operation cannot be instructed to land and hold short of an intersecting runway.

Thanks for clarification. I knew bits and pieces, but just wanted to advise I've heard it before.
 
Thanks for info and explanation. Appreciate it
 
My apologies if this is a really stupid question, but how did the controller know that the Embraer was a Part 121 operator?
 
My apologies if this is a really stupid question, but how did the controller know that the Embraer was a Part 121 operator?

There are generally a few hints. Such as the aircraft operating under an air carrier callsign, with an air carrier flight number, and that particular combination showing up on a regular basis.
 
Back
Top