Database Update Thursday Morning 0901z
based on Departure Time, not Arrival.

___________________________________

.3 RNP & RNAV Visuals - A320/321

Remember, for RNAV Visuals, it is not required to enter .3 RNP on the Prog page during the setup, unless ".3 RNP Required" is shown on the Approach Chart.  Entering the .3 RNP, simply triggers the "Accuracy Low. GPS Primary Lost" message.  On all RNP Approaches, and selected RNAV Approaches in some cases, this would require a Missed Approach, but not on an RNAV Visual.

Bottom line ... .3 RNP is required on any RNAV or RNP Instrument Approach.  The RNAV Visual is not an instrument approach.

Lowest Usable Flight Levels
Here's a really useless fact.
On the CAMRN # Arrival into JFK, there is a note that we all know about.  Expect to cross HOGGS at FL180 or the lowest usable Flight Level.

When the altimeter setting is below 29.92, FL180 is not usable, so we use FL190. The little known part is that this is based on the altimeter setting at ACY, not JFK. So, during your setup, and the JFK Altimeter setting is close to 29.92,  if you want to be a step ahead, check the ACY ATIS for the final decision or to avoid some confusion.

Landing and Takeoff Data
Wet or Dry?

This not really a little known fact, but worth thinking about.  For Takeoff, Aerodata defaults to a DRY runway, and you must manually select WET for a wet runway, but the TLR numbers are based on a WET Runway, should you need to use those.  For Landing, it's just the opposite ... Aerodata defaults to a WET Runway, (RCC=5) and you must select DRY (RCC=6), if you need dry numbers.  It is perfectly OK to use WET numbers on a DRY runway for landing, but keep in mind you have the option of forcing it to DRY, RCC=6 if needed for a short runway, at max landing wt, on a hot day, for example.

Feel free to contact me with any other topics

you would like to see discussed here on
BlueBrief.

BlueBrief on Mobile

Safari on the iPad seems to work just fine.

Your feedback is always welcome and actually very helpful.