RNAV / RNP And navigation Flashcards

1
Q

Confirmation at compulsory reporting points / points of HDG change?

A

Mutual confirmations:

  • confirmation of point overflown
  • confirmation of NAV mode SW( ie LNAV / HDG)

Also needs to be done after deviation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Flight planning requirements to use GPS for RNAV as Primary NAV sensor ?

A
  • confirm availability of GPS
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What is RNAV (Area Navigation)?

A

Method of navigation permitting aircraft to determine its position and fly on desired route by using NAVAIDs, GPS or Internal Navigation (INS)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What is difference between RNAV and RNP?

A

RNP requires an onboard performance monitoring and alerting system

RNAV has no requirement for onboard performance monitoring or alerting

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Each RNP type and uses?

A

Basic RNP 1 / RNP 1 = Enroute / terminal
RNP 2 = Oceanic / Remote
RNP 4 = Oceanic / Remote

RNP APP = approach procedure
RNP AR = Approval required approach

RNP 10 is same as RNAV 10 so no reporting / alerting required

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Each RNAV type and uses?

A

RNAV 1 = Enroute / terminal
RNAV 2 = Enroute / terminal
RNAV 5 = Enroute / terminal

RNAV 10 (RNP 10) = Oceanic / Remote

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Navigation sensors required for each RNAV/RNP?

A

All require GPS!

RNAV 1/2 = GPS, DME/DME/IRU (DME/DME other than Japan)

RNAV 5 = GPS, DME/DME, VOR/DME, INS/IRS

RNAV 10 (RNP 10) = GPS, INS/IRS

BASIC RNP1 / 2 / 4 / APP = GPS only!

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Checking Integrity of Navigation sensors?

A

GPS - by RAIM prediction (not required if other sensor used and GPS not required)
DME GAP - IRU required or GPS

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

2 types of GPS approaches ?

A

GPS overlay APP:

  • none in japan
  • same as non precision approach (procedure /WX minima)
  • Must still have all NAVAIDs required available for approach (during initial / intermediate approach)
  • not just depend on GPS (check accuracy with navaids)

GPS stand alone APP:

  • no NAVAIDs required (solely flown using GPS only) unless MAP requires them
  • its own procedure and WX minima
  • must have GPS accuracy from IAF and whole APP
  • 2 vertical path options:
  1. LNAV = only considers protected airspace for step down
  2. LNAV/VNAV (BARO-VNAV APP) = considers VNAV path at constant descent path
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

RNAV Alternate airport requirements ?

A
  • At least 1 (NON GPS) INST APP must be available for takeoff / enroute alternate airport
  • but exemptions if not available (at least 1 stand alone GPS app required):
  1. Only 1 airport using stand alone GPS available for enroute alternate (if multiple alternates enroute)
  2. DEST / DEST ALTN an Takeoff ALTN airport must have other than GPS approach available
  3. IF Enroute ALTN has other approaches can be not available if NAVAIDs U/S
  4. Check RAIM (FLT planning) available at enroute ATLN
  5. Check RAIM at least 1 more time during flight to confirm availability of GPS

Only following airport available takeoff ALTN / enroute ALTN:

  1. Majuro (PKMJ)
  2. Midway (PMDY)

Only available if:

  1. 2 sets INS working
  2. WX > CIG 1000ft / VIS 5000m (3SM) at ETA
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Can you use GPS in state that doesn’t use WGS-84 for geographic reference?

A

Yes (check error and position info but)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Lateral guidance modes for B787 during RNAV operations?

A

LNAV or FAC

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Self Contained Navigation requirements (pre / inflight)?

A

Preflight - 2 sets of INS at time of departure

During flight (before reaching self contained nav point):

  • 2 sets operating normally can continue
  • must divert / change route if less than 2 sets

During flight (after passing Self Nav point):

  • continue if 2 sets operating normally
  • if less than 2 - PIC discretion (continue / divert / return) based on WX etc
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

If only 1 INS system operating inflight (ie 1 fails) ?

A

Prepare for all to fail:

  • confirm A/C position (plot it)
  • look for available NAVAIDS
  • use WX radar
  • if INS unreliable (DISC AP) and fly HDG to next reporting point
  • Obtain info from ATC
  • perform DR
  • Check latest wind
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Procedures if all INS system fail?

A
  • Request radar vector (if radar coverage)
  • use WX radar
  • look for NAVAIDs
  • use DR (check last POS)
  • request info from other A/C / ATC
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

B787 Composition of INS System?

A

1 set = 1x FMC + 1 x IRU

2 sets = 2 x FMC (only 1 MFD / keyboard required) + 2 x IRU

Or 2 x FMC (only 1 MFD / keyboard required + 1x IRU + 1 x AHRU (1 GPS)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Terminal area / enroute RNAV checks in FMS?

A

Terminal:

  • route on MAP / PLN matches with SID / APP
  • waypoint sequence correct
  • no discontinuities
  • which waypoints fly by / fly over
  • speed and altitude constraints

Enroute :

Check FLT PLN with MAP / PLN

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Maximum difference in track in FMC to FLT PLN ?

A

3’ on less is ok from magnetic variation and not considered defect

Nav database if current will be up to date with current variation (chart may not)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Can manual entry of new / created waypoints be used in FLT PLN?

A

No - unless PACOTS or UPR route

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Checking step down fix in RNAV / RNP APP?

A
  • should follow chartered ALT restrictions rather than the NAV database (unless doing BARO-VNAV APP)
  • the NAV database may not have all step down restrictions
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

Which aircraft are ETOPs approved?

A

All 180mins unless NOTAM (group 1,2,3) and group 4 is 140 mins

Intermix and all ENG for international ops 180 min now A,C, D, K , L

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

Confirmation of GPS availability?

A

24 satellites in 6 orbital planes- 4 each plane (there is 32 total in constellation)

So at least 6 can be used from any corner of earth at once

Pre flight : minimum 23 checked by NOTAM

Applicable for routes - RNAV 1, 2 , RNP 2/4, RNAV 5, RNAV without accuracy

23
Q

If GPS satellites less than 23?

A

Pre flight :

  • change route and re check 23 or above
  • or check RAIM (change route to avoid RAIM hole)

Inflight:

  • check RAIM adjust flight time / route to avoid RAIM hole or change route to not require GPS
24
Q

RAIM Check procedures?

A
  • if RAIM outages of more than 5 mins will be issued by NOTAM for each phase of flight (APP, terminal, Enroute)

If APP requires less than 0.3nm the accuracy value will be stated.

If RAIM hole > 5 mins must check not during time of GPS as primary NAV sensor if so adjust time / route to other not requiring GPS

RAIM prediction should be done 15 mins before / after ETA for GPS stand alone APP.

If Initial / intermediate app segments require RNAV / RNP 1 must be checked

25
Q

Do you have to check RAIM again if delayed?

A

Yes need to check again unless no possibility of encountering RAIM hole

Notified by dispatcher if new RAIM outages

26
Q

What is RAIM and FDE?

A

RAIM = Receiver Autonomous Integrity Monitoring

RAIM algorithm requires 5 satellites minimum to detect loss of integrity (loss of RAIM) also provide alert if accuracy not met.

FDE = Fault Detection + Exclusion

Uses minimum 6 satellites to detect and exclude any faulty satellite

27
Q

What happens when loss of GPS integrity?

A
  • Means loss of GPS function (not necessarily loss of position information)
  • RAIM function determines use of GPS not appropriate and then RNAV equipment change NAV sensor from GPS to another one (IRS)

IRS can determine aircraft position without GPS or NAVAIDs

monitor - ANP, NAV Sensor ND / FMC and WX condition

28
Q

RNAV 1/2 Operational Procedures :

A

Preflight :

  • Check GPS availability (RAIM)
  • when DME/DME or DME/DME IRU used as primary NAV sensor = max DME GAP 14nm
  • “R” in clock 10 ATS FLT PLN
  • “D1” (RNAV 1) / “C1” (RNAV 2) in block 18 after PBN of aircraft capable

Before Departure:

  • NAV database current
  • GPS updating (before takeoff roll) if primary NAV sensor

Before commencing :

  • verify required equipment operating normally
  • FMC route / RWY and name matches chart on MAP
  • use AP/FD in LNAV/FAC (no need RNAV 2 unless can monitor dev on MAP)
  • review contingency (alternate star / Sid / APP) not requiring RNAV)
29
Q

How to update GPS in B787 / shift distance?

A

Can commence takeoff roll if not using GPS primary sensor if:

Check shift distance in route manual to correct aircraft position and enter to CDU if > 1000ft and:

Auto updates TOGA SW push on takeoff roll

30
Q

Unable RNAV/RNP?

A

If ANP exceeds RNP = notify ATC “unable RNAV / RNP” request radar vector

RNAV 1/2 : DME Gap exceeds 14nm without conducting RAIM check in case of failure of critical DME = advise ATC and request radar vector (N/A if can check RAIM)

RNAV 5 : DME gap exceeds 100nm notify ATC / request radar vector and check RAIM (if checked can continue)

Make report (company to notify JCAB)

31
Q

Required onboard equipment RNAV 1/2?

A

FMC x 2
IRU x 1
DME x 1

Or

FMC x 2
IRU x 1
GPS x 1

32
Q

RNAV 5 operational procedures ?

A

Preflight :

  • Check GPS availability (RAIM)
  • when DME/DME or VOR/DME used as primary NAV sensor = NAVAIDs required max DME GAP 100nm
  • “R” in clock 10 ATS FLT PLN
  • “B1” (RNAV 5) in block 18 after PBN of aircraft capable

Before Departure:

  • NAV database current

Before commencing :

  • verify required equipment operating normally
  • FMC route matches FLT PLN on MAP
  • use AP/FD in LNAV/FAC (no need RNAV 5 unless can monitor dev on MAP)
33
Q

Required onboard equipment RNAV 5?

A

FMC x 2
IRU x 1
VOR x1
DME x 1

Or

FMC x 2
IRU x 1
GPS x 1

34
Q

RNAV 10 (RNP10) Operational Procedures:

A

Preflight :

  • Check aircraft approved (flight time / Route eligibility)
  • “R” in clock 10 ATS FLT PLN
  • “A1” (RNAV 10/RNP10) in block 18 after PBN if aircraft capable

Before Departure:

  • NAV database current

Before commencing :

  • verify required equipment operating normally
  • FMC route matches FLT PLN on MAP
  • use AP/FD in LNAV/FAC (no need RNAV 10 unless can monitor dev on MAP)
    -cross check NAVAID position updating within time limits (18 min DME/DME or VOR/DME 30 min

If route not eligible; change route off RNAV 10

35
Q

Required onboard equipment for RNAV 10(RNP 10)?

A

Unlimited FLT Time:

FMC x 2 (1 MFD and keyboard required)
IRU x 2
GPS x 1

Or IRU x1 and AHRU x 1 and GPS x 1

18hrs flight time:

FMC x 2 (1 MFD and keyboard required)
IRU x 2

(If IRS alignment done between 65 N and 65S)

36
Q

RVSM Operating Procedures?

A

FLT planning:

  • check aircraft approved (W) item 10 ATS FLT PLN
  • reported and forecast WX Enroute
  • confirm onboard equipment serviceable
  • if MEL must be no restriction on RVSM + nothing reported to maintenance
  • FL290-410 and boundary

Before departure :

  • check journey log still ok and onboard equipment
  • exterior inspection Check static sources clear
  • check primary altimeters within 75ft of ELEV (if out can check again by takeoff)

Before RVSM entry :

  • confirm onboard equipment and check altimeter settings
  • level off overshot 150ft max
  • record altimeter differences TOC in case needed for contingency
  • comply with contingency for WX / emergency descent in oceanic
  • 1hr intervals cross check altimeter settings (max difference 200 ft)

Check not required due B787 altitude comparison function.

1 hour check required if EICAS “NAV AIR DATA SYS”

37
Q

Report “Negative RVSM” to ATC when?

A
  1. Unable to maintain assigned altitude and follow ATC instructions
  2. Failure of Altitude reporting system
  3. Unable to determine altitude from 2 primary Altimeters (LAND ASAP)
  4. Failure both transponders
    5, loss of thrust / equipment requiring descent
  5. Greater than moderate turbulence

If unable contact ATC apply contingency for that airspace

38
Q

What to enter in journey log if RVSM failure ?

A
  1. Primary / secondary altimeter setting / reading
  2. Altitude selector reading
  3. AP used
  4. Altimeter differences (including ALTN selector)
  5. Transponder used and info from ATC regarding ALT
39
Q

Required onboard equipment for RVSM?

A
  1. Transponder x 1
  2. FCM (for ADR) x 1
  3. Static port x 2 + Pitot x 2 (if no EICAS “NAV AIR DATA SYS” then both operating normally)
  4. PFD x 2 (altitude)
  5. Altitude Alerting system x 1
  6. Alt Hold function x 1 (includes VNAV, VS, FPA)
40
Q

Equipment required for CPDLC?

A
  • Datalink x1
  • MFD x 1 (including keyboard) + cursor)
  • Satcom x 1 (for satcom use)
  • VHF x 1
41
Q

ADS-B OUT Operational Procedures ?

A
  • “L” + “B1” in block 10 of ATS FLT PLN
  • Check FLT number entered into FMS matches ATS FLT PLN
  • Confirm onboard equipment required operating + continuous comms (VHF/HF/CPDLC)
  • Notify ATC if negative ADS-B (may need to change route) + submit report
42
Q

ADSB-OUT required onboard equipment ?

A
  1. Transponder x 1
  2. GPS x 1
  3. FMC x 1
43
Q

Portable EFB Operating Procedures ?

A
  • Needs to be stowed (check sticky suction status pre flight) or in flight bag
  • Can be hand held when: comparing ND/CDU, briefing, calculating performance, PM confirm POS taxiing (avoid in turbulence)
  • Can’t be held on final approach
  • prevent both heads down / hand over control
  • If fails stop using device
  • Used as primary device (paper backup and then FMS)
  • must be up to date (databases)
  • documents required loaded

If all conditions not met - use spare or paper charts

44
Q

EFB Applications approved for use?

A
  • Smart Catalog
  • JEP FD
  • OPT
  • Adobe + Foxit +. iBooks
45
Q

Required onboard equipment for RNAV operations without designated NAV accuracy ?

A
  • FMC x 2
  • IRU x 1
  • VOR x 1
  • DME x 1
  • GPS x 1
  • Autopilot x 1
46
Q

Operational Procedures for RNAV ops without designated NAV accuracy?

A
  • IF GPS used Primary NAV Sensor - check RAIM (not required for GPS overlay APP)
  • verify proper NAV accuracy entered into FMC (or do manually)
  • RNAV APP - check name and procedure correct and verify ND
  • If unable RNAV notify ATC and request radar vector
47
Q

BASIC RNP 1 Operating Procedures ?

A

Preflight :

  • Check GPS availability (RAIM)
  • “R” in block 10 ATS FLT PLN
  • “O1” (RNP 1) in block 18 after PBN of aircraft capable

Before Departure:

  • NAV database current
  • verify GPS updating on before takeoff roll

Before commencing :

  • verify required equipment operating normally
  • FMC route / RWY and name matches chart on MAP
  • use AP/FD in LNAV/FAC
  • SID/STAR/IAP = verify RNP value 1nm (manual entry if needed)
  • Cross track error within +/- 0.5nm ( in turns up to +/- 1nm)
  • review contingency (alternate star / Sid / APP) not requiring RNP or notify ATC > radar vectors
48
Q

Required onboard equipment for BASIC RNP 1?

A
  • FMC x 2 (including 2 x CDU)
  • IRU x 2
  • GPS x 2
  • ND x 2

Or

  • FMC x 2 (including 2 x CDU)
  • IRU x 1
  • AHRU x 1
  • GPS x 2
  • ND x 2
49
Q

Required onboard equipment for RNP 2?

A
  • FMC x 2
  • IRU x 2
  • GPS x 2
  • ND x 2

Or

  • FMC x 2
  • IRU x 1
  • AHRU x 1
  • GPS x 2
  • ND x 2

Same as RNP1 but no requirement for 2 x CDU

50
Q

RNP 2 Operational Procedures ?

A

Preflight :

  • Check GPS availability (RAIM)
    (No RNP 2 specific items in block 10 or 18)

Before Departure:

  • NAV database current

Before commencing :

  • verify required equipment operating normally
  • FMC route matches FLT PLN
  • use AP/FD in LNAV/FAC
  • verify RNP value 2nm (manual entry if needed)
  • Cross track error within +/- 1nm ( in turns up to +/- 2nm)
  • review contingency (alternate route) not requiring RNP or contact ATC
51
Q

RNP 4 Operational Procedures ?

A

Preflight :

  • Check GPS availability (RAIM)
  • “R” in block 10 ATS FLT PLN + “L1” in block 18 after PBN if aircraft capable

Before Departure:

  • NAV database current

Before commencing :

  • verify required equipment operating normally
  • verify GPS updating
  • FMC route matches FLT PLN
  • use AP/FD in LNAV/FAC
  • verify RNP value 4nm (manual entry if needed)
  • Cross track error within +/- 2nm ( in turns up to +/- 4nm)
  • review contingency (alternate route) not requiring RNP or contact ATC
52
Q

Required onboard equipment for RNP 4?

A
  • FMC x 2
  • IRU x 2
  • GPS x 2
  • ND x 2

Or

  • FMC x 2
  • IRU x 1
  • AHRU x 1
  • GPS x 2
  • ND x 2

If 1 GPS fails - continue RNAV10 (RNP10) operations

Same as RNP1 but no requirement for 2 x CDU

53
Q

RNP Approach required onboard equipment?

A
  • FMC x 2
  • IRU x 2 (or IRU x 1 + AHRU x 1)
  • GPS x 2
  • ND x 2
  • Autopilot x 1

(No requirement for 2 CDU)

54
Q

RNP Approach Operational Procedures ?

A

Preflight :

  • Check GPS availability (RAIM)
  • “R” in block 10 ATS FLT PLN and “S2” block 18 after PBN if aircraft capable

Before Departure:

  • NAV database current

Before commencing :

  • verify required equipment operating normally
  • verify GPS updating
  • APP in FMC name and route matches chart and verified ND
  • use AP in LNAV/FAC
  • verify RNP value 0.3nm (manual entry if needed) for terminal (1nm Initial / intermediate)

During Approach:

  • Cross track error within 1/2 RNP ie 0.5nm (+/- 0.15nm after FAF ( in turns up to +/- 1nm initial / intermediate / MAP and 0.3nm FAF)
  • Must be established on FAC no later than FAF before starting descent (ensures terrain clearance)

When to conduct MAP:

  • “NAV UNABLE RNP”
  • Cross track error exceeds 1 x RNP (1nm or 0.3nm after FAF)
  • Cannot monitor cross track on Map display or NPI (NAV PERF Indicator)
  • Unstable APP or ATC