When in doubt... (long)

Teller1900

En-Route
Joined
Aug 4, 2007
Messages
3,644
Location
Denver, CO
Display Name

Display name:
I am a dad!
...ASK the tower!

We were in the back of the seemingly endless line of planes trying to get the heck out of Newark night before last when we got to listen in on a very unfortunate exchange between a freight dawg and Newark tower (I'm sure it can all be found on liveATC, I just haven't had time to go find it - 21 Jan at 2150ish local).

Wiggins 17-something-something, a Cessna Caravan, made a decently soft landing on runway 11 and received instructions to keep it rolling through the 22R intersection, make a right on Papa, and hold short of Yankee. Not too difficult. Now at this point, EWR was departing all traffic from 22R at intersection Whiskey and landing 22L. This means R, S, A, and B are all full of planes trying to get to the intersection of W and R, and thus to the runway, which is why it was a pretty big problem when he exited runway 11 on Romeo. Being head to head with a heavy 757 and no way out isn't someplace most people would want to be.

As soon as he started to make the turn, whichever plane was at the head of the line keyed their mic and said "you were supposed to cross 22R." Unfortunately the tower controller was busy spacing a couple planes on final and missed the call until the Van driver had already completed the turn. Rather than fessing up at this point, the Van driver remained silent until the tower figured out what had happened and told him to make a 180, right turn onto 11, and hold short of 22R for departing traffic. The Van's read back was atrocious, and barely understandable, but he did at least say the words "hold short" and "22R".

Nevertheless he headed right out onto 11 and across 22R. Almost as soon as he made the turn onto 11, the first plane in line advised the tower that "he's crossing 22R!"

This caused a problem. Not only had he been told to hold short, there was a 757 on 22R, not more than a couple hundred feet from this unfortunate Van, that had just been cleared for takeoff. The tower yelled at him to stop a few times, but he didn't seem to get the hint until he was right behind the 75-. This pilot, already having a pretty bad night, just found out what wake turbulence really means.

The 757 got off the ground with no problem, but the problems for the Cessna were only just begining. The tower finally got him to finish crossing 22R and onto Papa where he told the pilot to "just stop there." The next thing tower said was "any Port Authority vehicles on my frequency?" Ouch. Bad night for the freight dawg.

About ten minutes pass and the Tower has traffic moving on all three runways again. The Van is still parked just south of 11 on Papa. We're number 6 for departure. Then suddenly the Van driver gets brave (stupid?). "Newark Tower, Wiggins 17[something-something], on Papa holding short of Whiskey."

Oh buddy...just be quiet for a while. "Yeah, just hold there!" The tower snaps. Well, long story slighty shorter; it's another 10-15 minutes before a Port Authority vehicle arrives on Papa to escort the Caravan to his parking spot at the FedEx ramp. It was no surprise to anyone on the frequency that the ground controller had "a phone number for [him] to copy due to a possible pilot deviation."

The moral of the story? When in doubt, especially when there are (multiple) runways involved, ASK THE TOWER. It's the same thing controllers have emphasized on every tour I've ever taken. They may sound a little snippy if they're busy, but they'd much rather have you ask for clarification or progressive taxi than have you wonder onto a runway or head to head with another plane. That's doubly true for single pilot operations that don't have the bennefit of someone who can keep their head on the taxi diagram.
 
I had a minor misunderstanding with the tower at DuPage last weekend and in hindsight realize I should have gotten a little more clarification. During my landing roll on 20R I was instructed to "turn right, taxi to the ramp behind the Citation." So I turn right and I'm head to head with the Citation which has just entered the taxiway from the ramp I'm headed to. At this point it wasn't at all clear how I was supposed to go behind the Citation without going under it first.

To be fair, had I thought carefully I would have realized it was likely the jet was headed for the north (arrival) end of the same runway I just landed on and that he would be turning onto taxiway 'W' to get there. And with that in mind I could have just stopped on the W-8 connector before reaching W, at which point I would indeed be taxiing "behind" the jet. I'm pretty certain that's what the controller assumed I would do.

Instead, thinking that the Citation was going to continue straight ahead I pulled over onto 'W' to get out of the jet's way. Unfortunately for all, I went to the right (reflex from driving in the USA) which put me exactly in the intended path of the jet. Once I got it all figured out I just crossed to the other side of the connector and let the Citation pass, but I'm sure the other pilot and the tower were not impressed with my ground navigation skills. Obviously, the best course of action on my part would have been a call to the tower as soon as I realized I didn't understand what they meant by "behind the Citation" when we were facing each other on the same taxiway. My only excuse is that I was in the middle of considering that the tower told me there were several FBOs on the field when I had checked Airnav prior to the flight and found only one.

http://204.108.4.16/d-tpp/0901/05104AD.PDF
 
For both of you: Aside from the, Ask the TWR, what were the lessons you learned?

Aside from ask the twr? If I had stopped long enough to think things through I suspect I would have figured out that it was very likely the Citation was going to make a left turn onto the taxiway I was about to cross. But the key point is that both the tower and I made assumptions about what the other was thinking and we were both wrong. The way to fix that is for whoever realizes this first (me in this case) to call the other for clarification.
 
Aside from ask the twr? If I had stopped long enough to think things through I suspect I would have figured out that it was very likely the Citation was going to make a left turn onto the taxiway I was about to cross. But the key point is that both the tower and I made assumptions about what the other was thinking and we were both wrong. The way to fix that is for whoever realizes this first (me in this case) to call the other for clarification.

I guess from my story I'd say 1) continuous communication and quickly asking/fessing up to questions/mistakes is important, 2) always have a taxi diagram handy at complex airports that you're not familiar with, 3)include runway layout, anticipated turnoff, and intitial taxi instructions as part of your arrival/approach briefing.

What else am I missing?
 
That's what I was thinking. I'm sure there are other lessons to be learned as well. Not wanting to put words into anyone's mouth.

That's long been SOP here, for good reason, I feel. "...11 is more than 5000 feet of dry, good braking action runway with a right turn off on Sierra if we use max braking/reverse, Romeo if not, Papa if I really screw it up. Alternately we could get a 180 on the runway with a left turn off on November or Sierra, either way joining either Whiskey or Yankee to head down to Uniform under the COA ramp procedures. We don't have a LAHSO, but we'll stop before 22R if possible..."

Was I missing any other lessons to be learned here?
 
As a point of clarification. I did not intend to lead, as if I had something in mind. I asked because I wanted to know too.

As far as did you miss something? Probably, due to the fallability of humans, but those things won't become known until they reveal themselves...like at 3 AM in bed. Correlation, baby!
 
As a point of clarification. I did not intend to lead, as if I had something in mind. I asked because I wanted to know too.

As far as did you miss something? Probably, due to the fallability of humans, but those things won't become known until they reveal themselves...like at 3 AM in bed. Correlation, baby!

:rofl: Fair enough. I didn't think you were leading but I wasn't quite sure...figured I'd ask! I'll let you know what else (aviation related) I come up at 3am.
 
That caravan pilot needs some recurrent training.

Asking is an unappreciated skill. In aviation in particular, there really isn't anything that's a stupid question. Only problem is that ATC or pilots sometimes answer questions with an attitude, and as a result, people don't want to ask anymore.

Moral of the story for me? Don't just ask, but also give a good answer when asked, even if the answer seems obvious.

-Felix
 
Good post, keeps us all thinking and taking the time to prepare.

Yesterday at ILG I was ready to go at Kilo and rwy 1, holding short for two inbound. The first, a cirrus who landed and made a left turn on Delta when instructed to turn right. The cirrus came to an immediate stop clear of the runway and asked to confirm the instruction. He was then told to 180 and cross 1. Meanwhile no. 2 to land, a citation I think, asks if the DQO DME is operational. The tower was nice and just advised OTS, no mention of reading the NOTAM. My lovely Bride comments don't you have to read all those note thingy's? :rolleyes: Yes hon, I read all those note thingy's and uncover the sheet on my knee board to show her my list.
 
I would like to be listening to both twr and gnd while taxiing, in order to get the whole flick, but anytime I've tried that at a busy place it gets confusing and the possibility of missed calls rises.
 
Back
Top