PPRuNe Forums - View Single Post - Approach Climb Gradient vs EOSID
View Single Post
Old 5th Apr 2011, 23:31
  #108 (permalink)  
aterpster
Guest
 
Join Date: Apr 2009
Location: On the Beach
Posts: 3,336
Likes: 0
Received 0 Likes on 0 Posts
g.f.:

KSAV RNAV (RNP) 27, why is there a "RF required" notations, as all the transitions to final seem to be RF legs?
I believe you mean Runway 28. Also, I believe you meant to ask why is there not an RF required notation. The entry from FEXEM does not require RF so instead of the procedure stating "GPS and RF Required" each IAF except for FEXEM should be annotated "RF Required." But, it is a third-party procedure and the FAA folks who develop FAA RNP AR procedures refuse to do any QC on third-party procedures. I forced Ball Note 5 "radar required" for FEXEM and UCETA, because I commented for my organization during coordination. But, I missed the RF notation screw-up. In any case, I'm not Jeppesen's or GE's QC guy. I believe this is a Jeppesen developed procedure (wearing their third-party developer hat, not their chart maker hat).
aterpster is offline