Baro or DH

[FAR 0]

Hi.

 

Do i have to manually set the Baro or DH (wich ever is used) on the FO-side? or will the FO automatic do this when set correctly in app brief?

[damienw 1]

Hi.

 

Do i have to manually set the Baro or DH (wich ever is used) on the FO-side? or will the FO automatic do this when set correctly in app brief?

 

Set it on the captains side and in the briefing panel.

[MarcM 0]

Hello Damien,

 

OK but .. you don't answer clearly at the question ! What about FO side ??

[byork 2,258]

I'd have to check the code, but I think the FO sets the selector to DA after you close the approach brief.

 

If you're going to do a CATII or CATIII, set his selector to DH.

[MarcM 0]

I'd have to check the code, but I think the FO sets the selector to DA after you close the approach brief.

 

Hello Bryan,

 

Just finished a flight and I confirm FO doesn't change the numbers just as well BARO as RADIO even after the approach brief.

The only solution I've founded is to put on the PMDG Options in the FMC (Bloc Simulation leg 1/3) the "SYNC CAPT AND STBY BARO on YES.

[aceridgey 330]

Radio is normally used for CAT II or CAT III.

 

Baro for CAT1.

 

 

Basically Radio is 'radio altitude' meaning the height above the ground, not 'altitude [msl].

 

This is used in poor visibility conditions [CATII +CATIII]

 

Baro used for 90%+ of landings and a CAT I

[Steven_Caffey 23]

The only solution I've founded is to put on the PMDG Options in the FMC (Bloc Simulation leg 1/3) the "SYNC CAPT AND STBY BARO on YES.

 

That actually is the option for syncing the Altimiters, not the minimums.

[MarcM 0]

That actually is the option for syncing the Altimiters, not the minimums.

 

Hello Steve,

 

Yes ... you're right. For the F/O's minimums nothing change after the approach check-list

[Steven_Caffey 23]

Of course, you don't actually need to set the FO's minimums since he uses the value in the briefing panel..