737NG MEL 34-36-02-03A
Thread Starter
Join Date: Apr 2015
Location: cairo
Posts: 3
Likes: 0
Received 0 Likes
on
0 Posts
737NG MEL 34-36-02-03A
HelloI am interested in what your CMEL says about MEL 34-36-02-03A on the 737-800
According to MMEL it may be inop provided enroute procedure doesn't require it's use
I Have seen some operators who add (Except for RNP1 PRNAV RNP Approach)
What is the reason behind that?
How would a single FMC affect RNP1 PRNAV or RNP Approach
Thanks
According to MMEL it may be inop provided enroute procedure doesn't require it's use
I Have seen some operators who add (Except for RNP1 PRNAV RNP Approach)
What is the reason behind that?
How would a single FMC affect RNP1 PRNAV or RNP Approach
Thanks
Join Date: Jan 2000
Location: FL410
Posts: 860
Likes: 0
Received 0 Likes
on
0 Posts
MMEL is master document.
An MEL can be more restrictive by adding additional limitations.
It can never be more lenient.
In reference to MMEL rev 60 (outdated), it refers to CDU/MCDU repair category C and 1 required for dispatch.
It means that with one CDU inoperative, only 1 pilot can enter information.
Some companies require a dual installation for RNP1 PRNAV RNP Approach types, thus requiring both CDU/MCDU to be operational
An MEL can be more restrictive by adding additional limitations.
It can never be more lenient.
In reference to MMEL rev 60 (outdated), it refers to CDU/MCDU repair category C and 1 required for dispatch.
It means that with one CDU inoperative, only 1 pilot can enter information.
Some companies require a dual installation for RNP1 PRNAV RNP Approach types, thus requiring both CDU/MCDU to be operational
