Flight Plan "Remarks"?

Well for what it's worth, I deal with air carriers all the time who file with RNAV equipment suffixes, and then say "unable" to an RNAV or GPS approach. I'm not sure exactly what's going on there, but it's nice for them to be able to accept direct clearances without interrogation by the controller.

We are and file /Q, all-though the FMS we use (Honeywell GNS-XLS) is only RNAV 2 certified per AC 90-100A, and the "AC 90-100A compliance list" (which lists the various types of GPS equipment and what they are allowed to do). Because of this, we can not accept any RNAV SIDS or STARS, though we can legally accept en-route clearances. Either way we are still /Q.

What gets us, is even if we explain this to a controller (clearance, center, approach) the explanation/message has no way of getting to the next controller down the line, and we are constantly having to deny every controller who tries to give us RNAV terminal arrivals as we go down the line. In the past, we have explained this to one controller, been told "ok we will keep the clearance you have on file," get handed off and immediately told by the next controller to get ready for new clearance instructions to fly the RNAV STAR.

Is there anything we can do to make the message more clear in the remarks section? It's a pain in the butt, and hogs up the airwaves way more then it needs to. Needless to say, we would love a different piece of equipment rather than our current GNS-XLS (such as a Universal).
We put "NO RNAV SID/STARS!!!" in our remarks; we thought we were really pushing it when we started putting the "!!!!" at the end. What I have come to learn lately is that controllers are relying on (using) RNAV SID/STAR's much more than before, and even some airports only have RNAV departures / arrival procedures. It makes for an interesting day to say the least.
 
I think that's about the best you can do really.

I agree. Some controllers really don't understand the complexities of the equipment suffix, even under the old system. Now that we're switching to ICAO, most are really going to be lost. I'm sorry to say that some don't care, either, and that's why your inability to perform RNAV SIDs/STARs isn't forwarded to the next controller.

That information should be forwarded; that's part of our job. Controllers hate extra landline phonecalls, so if you get a frequency change and the new controller tries to give you an RNAV SID/STAR after you just explained it to the last guy, tell the new controller to call the previous controller and query him. As Landis said, you could always try a fifth exclamation point, too.
 
We see them. The first I think 16 characters at least in terminal. MX test flight, multiple approaches, check ride etc are useful to add. It keeps us from sending you to your filed route out in East Jesus when all you really need is a pressurization check. The one time I saw checkride in the remarks I made absolutely sure the vectors were generous and easy and complimented the pilot on her skill on the tower handoff. I've seen a ton of RA(dar) VEC(tor) appreciated/equipped. That'll get you a sure shortcut with me. I've seen we love ATC in the remarks, or Merry Christmas during that season. Yes we see it.

Also, if you file via DUATS (I think that's the one) we see your full name autopopulated in the remarks. PIC John Doe etc. We have a guy that'll say "Hey John, turn ten left". "How do you know my name?" "Doe family reunion, I'm your third cousin, remember me?"

IFR Checkride...Thanks!....lead to:

Direct! Sure, No Problem! Anything else today?!
 
We have an unusual call sign. So we spell out the call sign, "Peregrine" in the remarks section. Funny thing is that we still get asked how to pronounce it. Some controllers are on to us, and know we keep a list of incorrect names. They come back a few times trying to see if they can add a new one. Penguin? yeah it on there. Pigeon? Yup already have it. Polygamy? Nope congrats, that's a new one.
 
Ha! Peregrine is the name of the street I live on. When I give out my address I get a lot if confused looks and "can you spell that?"
 
I like when pilots put what they want in the remarks. For example, "ILS, VOR, GPS at XXX." Then I don't have to ask what do you want.
 
We are and file /Q, all-though the FMS we use (Honeywell GNS-XLS) is only RNAV 2 certified per AC 90-100A, and the "AC 90-100A compliance list" (which lists the various types of GPS equipment and what they are allowed to do). Because of this, we can not accept any RNAV SIDS or STARS, though we can legally accept en-route clearances. Either way we are still /Q.

What gets us, is even if we explain this to a controller (clearance, center, approach) the explanation/message has no way of getting to the next controller down the line, and we are constantly having to deny every controller who tries to give us RNAV terminal arrivals as we go down the line. In the past, we have explained this to one controller, been told "ok we will keep the clearance you have on file," get handed off and immediately told by the next controller to get ready for new clearance instructions to fly the RNAV STAR.

Is there anything we can do to make the message more clear in the remarks section? It's a pain in the butt, and hogs up the airwaves way more then it needs to. Needless to say, we would love a different piece of equipment rather than our current GNS-XLS (such as a Universal).
We put "NO RNAV SID/STARS!!!" in our remarks; we thought we were really pushing it when we started putting the "!!!!" at the end. What I have come to learn lately is that controllers are relying on (using) RNAV SID/STAR's much more than before, and even some airports only have RNAV departures / arrival procedures. It makes for an interesting day to say the least.
We file /Q, RMK "RNVE99" which makes my girlfriend's dad (who does advanced automation) snicker, but gets the point across.
 
Back
Top