validation & implementation considerations 1 beijing, china; 30 jun-11 jul 2014

51
VALIDATION & VALIDATION & IMPLEMENTATION IMPLEMENTATION CONSIDERATIONS CONSIDERATIONS 1 1 ING, CHINA; 30 JUN-11 JUL 2014

Upload: lauren-newman

Post on 23-Dec-2015

215 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

VALIDATION & VALIDATION & IMPLEMENTATION IMPLEMENTATION CONSIDERATIONSCONSIDERATIONS

VALIDATION & VALIDATION & IMPLEMENTATION IMPLEMENTATION CONSIDERATIONSCONSIDERATIONS

11BEIJING, CHINA; 30 JUN-11 JUL 2014

Page 2: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

OBJECTIVEOBJECTIVEOBJECTIVEOBJECTIVE

This module provides an overview of This module provides an overview of airspace airspace concept and flight procedure validation and concept and flight procedure validation and considers aspects of considers aspects of PBN PBN iimplementation.mplementation.

This module provides an overview of This module provides an overview of airspace airspace concept and flight procedure validation and concept and flight procedure validation and considers aspects of considers aspects of PBN PBN iimplementation.mplementation.

22

Page 3: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

3

Airspace Concept Activity OverviewAirspace Concept Activity OverviewAirspace Concept Activity OverviewAirspace Concept Activity Overview

Page 4: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

Why do validation?Why do validation?Why do validation?Why do validation?

✈Validate Airspace Concept and resultingValidate Airspace Concept and resulting routes/instrument routes/instrument flight proceduresflight procedures

✈Assess if ATM objectives are achievedAssess if ATM objectives are achieved

✈ Confirm flyability of Instrument Flight ProceduresConfirm flyability of Instrument Flight Procedures

✈ Identify possible problems and develop mitigationsIdentify possible problems and develop mitigations

✈ Provide evidence design is safeProvide evidence design is safe

Validation is an ongoing processValidation is an ongoing process

✈Validate Airspace Concept and resultingValidate Airspace Concept and resulting routes/instrument routes/instrument flight proceduresflight procedures

✈Assess if ATM objectives are achievedAssess if ATM objectives are achieved

✈ Confirm flyability of Instrument Flight ProceduresConfirm flyability of Instrument Flight Procedures

✈ Identify possible problems and develop mitigationsIdentify possible problems and develop mitigations

✈ Provide evidence design is safeProvide evidence design is safe

Validation is an ongoing processValidation is an ongoing process

44

Page 5: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

CAUTIONCAUTIONCAUTIONCAUTION

GARBAGE IN GARBAGE IN GARBAGE IN GARBAGE IN

55

RUBBISH OUT!!!RUBBISH OUT!!!

Page 6: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

Validation methodsValidation methods Validation methodsValidation methods

Airspace ConceptAirspace Concept✈ Chalk and talkChalk and talk✈ ModellingModelling✈ FTSFTS✈ RTSRTS

Airspace ConceptAirspace Concept✈ Chalk and talkChalk and talk✈ ModellingModelling✈ FTSFTS✈ RTSRTS

66

Flight ProceduresFlight Procedures✈ PC based simulationPC based simulation✈ Flight simulatorsFlight simulators✈ Ground checksGround checks✈FMS simulatorFMS simulator✈ Live trialsLive trials

Page 7: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

CHALK and TALKCHALK and TALKCHALK and TALKCHALK and TALK

77

Page 8: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

Airspace Concept ValidationAirspace Concept ValidationAirspace Concept ValidationAirspace Concept Validation

✈ General ConsiderationsGeneral Considerations

✈Aircraft performanceAircraft performance

✈ Sterile environment?/Secondary trafficSterile environment?/Secondary traffic

✈ Special eventsSpecial events

✈ General ConsiderationsGeneral Considerations

✈Aircraft performanceAircraft performance

✈ Sterile environment?/Secondary trafficSterile environment?/Secondary traffic

✈ Special eventsSpecial events

88

Page 9: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

Advantages of ModelingAdvantages of ModelingAdvantages of ModelingAdvantages of Modeling

✈ FlexibleFlexible

✈ SimpleSimple

✈ ‘‘What ifWhat if’’ investigations investigations

✈ Easy to test large number of traffic samplesEasy to test large number of traffic samples

✈ Data derived from real traffic and ATC Data derived from real traffic and ATC environmentenvironment

✈ FlexibleFlexible

✈ SimpleSimple

✈ ‘‘What ifWhat if’’ investigations investigations

✈ Easy to test large number of traffic samplesEasy to test large number of traffic samples

✈ Data derived from real traffic and ATC Data derived from real traffic and ATC environmentenvironment

99

Page 10: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

EXAMPLEEXAMPLEEXAMPLEEXAMPLE

1010

Page 11: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

Modeling - LimitationsModeling - LimitationsModeling - LimitationsModeling - Limitations

✈ CrudeCrude

✈ Only high level dataOnly high level data

✈ Basic aircraft performanceBasic aircraft performance

✈ Does not replicate controller interventionsDoes not replicate controller interventions

✈ Simplified Simplified

✈ SubjectiveSubjective

✈ CrudeCrude

✈ Only high level dataOnly high level data

✈ Basic aircraft performanceBasic aircraft performance

✈ Does not replicate controller interventionsDoes not replicate controller interventions

✈ Simplified Simplified

✈ SubjectiveSubjective

1111

Page 12: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

Fast Time Simulation (FTS)Fast Time Simulation (FTS)Fast Time Simulation (FTS)Fast Time Simulation (FTS)

✈Used for sector capacityUsed for sector capacity

✈Quality dataQuality data

✈ FlexibleFlexible

✈Good acceptance of resultsGood acceptance of results

✈ Evaluate TLSEvaluate TLS

✈Used for Safety CaseUsed for Safety Case

✈Used for sector capacityUsed for sector capacity

✈Quality dataQuality data

✈ FlexibleFlexible

✈Good acceptance of resultsGood acceptance of results

✈ Evaluate TLSEvaluate TLS

✈Used for Safety CaseUsed for Safety Case

1212

Page 13: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

FTSFTSFTSFTS

1313

Page 14: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

FTS - LimitationsFTS - LimitationsFTS - LimitationsFTS - Limitations

✈Simplified modelSimplified model

✈Only statistical dataOnly statistical data

✈No active controller interaction during FTSNo active controller interaction during FTS

✈Accuracy of models is keyAccuracy of models is key

✈Aircraft performanceAircraft performance

✈Met conditionsMet conditions

✈Simplified modelSimplified model

✈Only statistical dataOnly statistical data

✈No active controller interaction during FTSNo active controller interaction during FTS

✈Accuracy of models is keyAccuracy of models is key

✈Aircraft performanceAircraft performance

✈Met conditionsMet conditions

1414

Page 15: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

Real Time Simulation (RTS)Real Time Simulation (RTS) Real Time Simulation (RTS)Real Time Simulation (RTS)

✈Best method to simulate ATC trialsBest method to simulate ATC trials✈High quality dataHigh quality data✈Feed controllers/ pseudo pilotsFeed controllers/ pseudo pilots✈Human factorHuman factor✈Can be part of Safety CaseCan be part of Safety Case✈No risk to live opsNo risk to live ops✈Unlimited scopeUnlimited scope

✈Best method to simulate ATC trialsBest method to simulate ATC trials✈High quality dataHigh quality data✈Feed controllers/ pseudo pilotsFeed controllers/ pseudo pilots✈Human factorHuman factor✈Can be part of Safety CaseCan be part of Safety Case✈No risk to live opsNo risk to live ops✈Unlimited scopeUnlimited scope

1515

Page 16: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

RTS - Limitations RTS - Limitations RTS - Limitations RTS - Limitations

✈ Limited scopeLimited scope

✈Designed for training ATCDesigned for training ATC

✈Aircraft performance not representativeAircraft performance not representative

✈Not designed for post simulation evaluation needed Not designed for post simulation evaluation needed for Airspace concept evaluationfor Airspace concept evaluation

✈ Limited scopeLimited scope

✈Designed for training ATCDesigned for training ATC

✈Aircraft performance not representativeAircraft performance not representative

✈Not designed for post simulation evaluation needed Not designed for post simulation evaluation needed for Airspace concept evaluationfor Airspace concept evaluation

1616

Page 17: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

Flight SimulatorFlight SimulatorFlight SimulatorFlight Simulator

✈High quality dataHigh quality data

✈ Confirm design aspectsConfirm design aspects

✈Fly-abilityFly-ability

✈EfficiencyEfficiency

✈Met impactMet impact

✈ Possible link to RTSPossible link to RTS

✈High quality dataHigh quality data

✈ Confirm design aspectsConfirm design aspects

✈Fly-abilityFly-ability

✈EfficiencyEfficiency

✈Met impactMet impact

✈ Possible link to RTSPossible link to RTS

1717

Page 18: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

Flight Simulator - LimitationsFlight Simulator - LimitationsFlight Simulator - LimitationsFlight Simulator - Limitations

✈Manual data collectionManual data collection

✈ For range of aircraft types/meteo conditions time For range of aircraft types/meteo conditions time consuming and expensive consuming and expensive

✈ Pilots needed to fly the simulatorPilots needed to fly the simulator

✈Manual data collectionManual data collection

✈ For range of aircraft types/meteo conditions time For range of aircraft types/meteo conditions time consuming and expensive consuming and expensive

✈ Pilots needed to fly the simulatorPilots needed to fly the simulator

1818

Page 19: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

Concept Validations ComparedConcept Validations ComparedConcept Validations ComparedConcept Validations Compared

1919

Page 20: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

Live ATC TrialsLive ATC TrialsLive ATC TrialsLive ATC Trials

✈Most accurate Most accurate

✈Real dataReal data

✈Feedback from all usersFeedback from all users

✈Most accurate Most accurate

✈Real dataReal data

✈Feedback from all usersFeedback from all users

2020

Page 21: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

Live ATC Trials - LimitationsLive ATC Trials - LimitationsLive ATC Trials - LimitationsLive ATC Trials - Limitations

✈Safety mitigations requiredSafety mitigations required

✈High detail required – large effort for a High detail required – large effort for a concept evaluationconcept evaluation

✈Limited scopeLimited scope

✈Limited flexibilityLimited flexibility

✈Safety mitigations requiredSafety mitigations required

✈High detail required – large effort for a High detail required – large effort for a concept evaluationconcept evaluation

✈Limited scopeLimited scope

✈Limited flexibilityLimited flexibility

2121

Page 22: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

Procedure ValidationProcedure ValidationProcedure ValidationProcedure Validation

2222

Page 23: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

Procedure ValidationProcedure ValidationProcedure ValidationProcedure Validation

✈Ground ValidationGround Validation✈Obstacle clearanceObstacle clearance

✈Charting Charting

✈CodingCoding

✈FlyabilityFlyability

✈Ground ValidationGround Validation✈Obstacle clearanceObstacle clearance

✈Charting Charting

✈CodingCoding

✈FlyabilityFlyability

2323

Page 24: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

Procedure ValidationProcedure ValidationProcedure ValidationProcedure Validation

✈Flight ValidationFlight Validation

✈Data verificationData verification

✈Obstacle verification (optional)Obstacle verification (optional)

✈Flyability (workload, charting, Flyability (workload, charting,

manoeuvring)manoeuvring)

✈InfrastructureInfrastructure

✈Database ValidationDatabase Validation

✈Flight ValidationFlight Validation

✈Data verificationData verification

✈Obstacle verification (optional)Obstacle verification (optional)

✈Flyability (workload, charting, Flyability (workload, charting,

manoeuvring)manoeuvring)

✈InfrastructureInfrastructure

✈Database ValidationDatabase Validation

2424

Page 25: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

Ground ValidationGround Validation✈ Obstacle clearance Obstacle clearance

✈ Independent review by procedure designer Independent review by procedure designer

✈ Charting Charting

✈ Independent reviewIndependent review

✈ Coding Coding

✈ Software tool Software tool

✈ Expert reviewExpert review

✈ Flyability – software tools (from PC-based to full flight simulator) Flyability – software tools (from PC-based to full flight simulator)

✈ Not necessarily an issue with standard procedures (e.g. ‘T’ approaches), Not necessarily an issue with standard procedures (e.g. ‘T’ approaches), but critical for some aircraft typesbut critical for some aircraft types

✈ Range of aircraft and meteo conditionsRange of aircraft and meteo conditions

✈ Obstacle clearance Obstacle clearance

✈ Independent review by procedure designer Independent review by procedure designer

✈ Charting Charting

✈ Independent reviewIndependent review

✈ Coding Coding

✈ Software tool Software tool

✈ Expert reviewExpert review

✈ Flyability – software tools (from PC-based to full flight simulator) Flyability – software tools (from PC-based to full flight simulator)

✈ Not necessarily an issue with standard procedures (e.g. ‘T’ approaches), Not necessarily an issue with standard procedures (e.g. ‘T’ approaches), but critical for some aircraft typesbut critical for some aircraft types

✈ Range of aircraft and meteo conditionsRange of aircraft and meteo conditions

25

Independent review – can be part of same organisation

Page 26: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

FlyabilityFlyabilityFlyabilityFlyability

✈ Independent assessmentIndependent assessment

✈Use of validation toolsUse of validation tools

✈Use of aircraft simulators Use of aircraft simulators

✈more than one typemore than one type

✈ Flight checksFlight checks

✈ Initial operational checksInitial operational checks

✈ Independent assessmentIndependent assessment

✈Use of validation toolsUse of validation tools

✈Use of aircraft simulators Use of aircraft simulators

✈more than one typemore than one type

✈ Flight checksFlight checks

✈ Initial operational checksInitial operational checks

2626

Page 27: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

Validation Tools /1Validation Tools /1Validation Tools /1Validation Tools /1

2727

Page 28: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

Validation Tools /2Validation Tools /2Validation Tools /2Validation Tools /2

2828

B737-300B737-300ISA +40ISA +40Wind 320/20Wind 320/20

B737-300B737-300ISA -20ISA -20Wind 250/25Wind 250/25

Page 29: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

Different Aircraft & Different Different Aircraft & Different ConditionsConditions

Different Aircraft & Different Different Aircraft & Different ConditionsConditions

2929

CA 500ft AGL; DF LL001; CA 500ft AGL; DF LL001; TF FARKS; TF…TF FARKS; TF…

No wind designed pathNo wind designed path

A319A319

B737/400B737/400

B747/400B747/400

A340/300A340/300

A320/319A320/319

Page 30: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

Wind EffectWind Effect Wind EffectWind Effect

3030

CA 500ft AGL; DF LL001; CA 500ft AGL; DF LL001; TF FARKS; TF…TF FARKS; TF…

Wind from 045Wind from 045°°

A319A319

B737/400B737/400

B747/400B747/400

A340/300A340/300

A320/319A320/319

Page 31: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

Mitigation by Speed Mitigation by Speed RestrictionRestriction

Mitigation by Speed Mitigation by Speed RestrictionRestriction

3131

CA 500ft AGL; DF LL001; CA 500ft AGL; DF LL001; TF FARKS [TF FARKS [210kts210kts]; TF…]; TF…

Wind from 045Wind from 045°°

A319A319

B737/400B737/400

B747/400B747/400

A340/300A340/300

A320/319A320/319

Page 32: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

Leg Length - Too ShortLeg Length - Too ShortLeg Length - Too ShortLeg Length - Too Short

3232

CA 2000ft AGL; DF BRW02CA 2000ft AGL; DF BRW02

No windNo wind

ATR42ATR42

B 747-400B 747-400

A340-300A340-300

2.7N2.7NMM

Page 33: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

Leg Length - AcceptableLeg Length - AcceptableLeg Length - AcceptableLeg Length - Acceptable

3333

CA 2000ft AGL; DF CA 2000ft AGL; DF BRW02BRW02

No windNo wind

ATR42ATR42

B 747-400B 747-400

A340-300A340-300

4.6N4.6NMM

Page 34: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

Flight Procedure ValidationFlight Procedure ValidationFlight Procedure ValidationFlight Procedure Validation

✈ Obstacle verification Obstacle verification

✈ Has full obstacle survey been completedHas full obstacle survey been completed

✈TAWS / GPWS alertsTAWS / GPWS alerts

✈ Flyability Flyability

✈Detailed workload and charting assessments Detailed workload and charting assessments

✈High level qualitative assessment of manoeuvring via High level qualitative assessment of manoeuvring via accurate flight simulator. accurate flight simulator.

✈ Infrastructure assessment Infrastructure assessment

✈Runway markings, lighting, communications, Runway markings, lighting, communications, navigation, etcnavigation, etc

✈ Obstacle verification Obstacle verification

✈ Has full obstacle survey been completedHas full obstacle survey been completed

✈TAWS / GPWS alertsTAWS / GPWS alerts

✈ Flyability Flyability

✈Detailed workload and charting assessments Detailed workload and charting assessments

✈High level qualitative assessment of manoeuvring via High level qualitative assessment of manoeuvring via accurate flight simulator. accurate flight simulator.

✈ Infrastructure assessment Infrastructure assessment

✈Runway markings, lighting, communications, Runway markings, lighting, communications, navigation, etcnavigation, etc

3434

Page 35: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

Flight InspectionFlight InspectionFlight InspectionFlight Inspection

✈ Flight Inspection often confused with ValidationFlight Inspection often confused with Validation

✈ Flight Inspection Addresses:Flight Inspection Addresses:✈ Navaid performance and receptionNavaid performance and reception for DME/DME for DME/DME

✈ Unintentional interferenceUnintentional interference for GNSS for GNSS

✈ Flight Validation may not fully address Navaid Flight Validation may not fully address Navaid Infrastructure issues Infrastructure issues (example: inspect DME/DME reception)(example: inspect DME/DME reception)

✈ Flight Inspection often confused with ValidationFlight Inspection often confused with Validation

✈ Flight Inspection Addresses:Flight Inspection Addresses:✈ Navaid performance and receptionNavaid performance and reception for DME/DME for DME/DME

✈ Unintentional interferenceUnintentional interference for GNSS for GNSS

✈ Flight Validation may not fully address Navaid Flight Validation may not fully address Navaid Infrastructure issues Infrastructure issues (example: inspect DME/DME reception)(example: inspect DME/DME reception)

3535

Page 36: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

Publication & Coordination Publication & Coordination with Data Houseswith Data Houses

Publication & Coordination Publication & Coordination with Data Houseswith Data Houses

3636

Page 37: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

RNAV Procedure DescriptionRNAV Procedure DescriptionRNAV Procedure DescriptionRNAV Procedure Description

✈ Procedures are currently published as charts and as textual Procedures are currently published as charts and as textual descriptions.descriptions.

✈ The charts are used by the pilots and ATC.The charts are used by the pilots and ATC.

✈ Database providers require clear, and unambiguous Database providers require clear, and unambiguous

procedure descriptions and use the charts to validate/check.procedure descriptions and use the charts to validate/check.

✈ Procedures are currently published as charts and as textual Procedures are currently published as charts and as textual descriptions.descriptions.

✈ The charts are used by the pilots and ATC.The charts are used by the pilots and ATC.

✈ Database providers require clear, and unambiguous Database providers require clear, and unambiguous

procedure descriptions and use the charts to validate/check.procedure descriptions and use the charts to validate/check.

3737

Page 38: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

RNAV Procedure DescriptionRNAV Procedure DescriptionRNAV Procedure DescriptionRNAV Procedure Description

✈ RNAV procedures defined by:RNAV procedures defined by:

✈ Sequence of waypointsSequence of waypoints✈IdentifierIdentifier✈Co-ordinatesCo-ordinates✈Fly-over/fly-by/fixed radiusFly-over/fly-by/fixed radius

✈Path Terminators - ARINC 424Path Terminators - ARINC 424

✈Altitude restrictionsAltitude restrictions

✈ Speed restrictionsSpeed restrictions

✈Direction of turnDirection of turn

✈Required navaidRequired navaid

✈ RNAV procedures defined by:RNAV procedures defined by:

✈ Sequence of waypointsSequence of waypoints✈IdentifierIdentifier✈Co-ordinatesCo-ordinates✈Fly-over/fly-by/fixed radiusFly-over/fly-by/fixed radius

✈Path Terminators - ARINC 424Path Terminators - ARINC 424

✈Altitude restrictionsAltitude restrictions

✈ Speed restrictionsSpeed restrictions

✈Direction of turnDirection of turn

✈Required navaidRequired navaid

3838

Page 39: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

ChartingCharting

39

Waypoint sequence

Fly-over/fly-by/fixed radius

Speed/Altitude Restrictions

Leg distance & magnetic track

Fix information

Turn direction

PT118 PT119

PT121PT120

203°

RW20

FAF

MAPt

113°293°

350°

4500

40005000

4000

PT125

169° ARZ 29.3NM236° ALM 27.4NM

Page 40: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

Procedure Description for Procedure Description for Database ProvidersDatabase Providers

Procedure Description for Procedure Description for Database ProvidersDatabase Providers

✈ Textual description is usually used to provide formal Textual description is usually used to provide formal statement of procedure.statement of procedure.

✈Often open to interpretation.Often open to interpretation.✈ RNAV procedures require more specific details including path RNAV procedures require more specific details including path

terminators.terminators.✈Can result in lengthy descriptions.Can result in lengthy descriptions.✈Alternative descriptive methods have been adopted by Alternative descriptive methods have been adopted by

OCP:OCP:✈Tabular layoutTabular layout✈Formalised textual descriptionFormalised textual description✈Formalised short-hand descriptionFormalised short-hand description

✈ Textual description is usually used to provide formal Textual description is usually used to provide formal statement of procedure.statement of procedure.

✈Often open to interpretation.Often open to interpretation.✈ RNAV procedures require more specific details including path RNAV procedures require more specific details including path

terminators.terminators.✈Can result in lengthy descriptions.Can result in lengthy descriptions.✈Alternative descriptive methods have been adopted by Alternative descriptive methods have been adopted by

OCP:OCP:✈Tabular layoutTabular layout✈Formalised textual descriptionFormalised textual description✈Formalised short-hand descriptionFormalised short-hand description

4040

preferred by data housespreferred by data houses

Page 41: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

Tabular DescriptionTabular Description

41

Page 42: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

Waypoint IdentificationWaypoint IdentificationWaypoint IdentificationWaypoint Identification

✈ IFPP introduced concept of strategic and tactical waypointsIFPP introduced concept of strategic and tactical waypoints

✈ Strategic waypoints:Strategic waypoints:

✈ identified by co-located navaid or by unique five-letter identified by co-located navaid or by unique five-letter pronounceable “name-code” (5LNC).pronounceable “name-code” (5LNC).

✈5LNCs may be misinterpreted when issuing “direct” or vector 5LNCs may be misinterpreted when issuing “direct” or vector instructions (ALECS, ALEKS, ALYKS).instructions (ALECS, ALEKS, ALYKS).

✈ Tactical Waypoints may be used in a specific terminal area for Tactical Waypoints may be used in a specific terminal area for vectoring, identification, and sequencing. vectoring, identification, and sequencing.

✈Tactical waypoint naming is specific to area.Tactical waypoint naming is specific to area.

✈ IFPP introduced concept of strategic and tactical waypointsIFPP introduced concept of strategic and tactical waypoints

✈ Strategic waypoints:Strategic waypoints:

✈ identified by co-located navaid or by unique five-letter identified by co-located navaid or by unique five-letter pronounceable “name-code” (5LNC).pronounceable “name-code” (5LNC).

✈5LNCs may be misinterpreted when issuing “direct” or vector 5LNCs may be misinterpreted when issuing “direct” or vector instructions (ALECS, ALEKS, ALYKS).instructions (ALECS, ALEKS, ALYKS).

✈ Tactical Waypoints may be used in a specific terminal area for Tactical Waypoints may be used in a specific terminal area for vectoring, identification, and sequencing. vectoring, identification, and sequencing.

✈Tactical waypoint naming is specific to area.Tactical waypoint naming is specific to area.

4242

Page 43: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

Strategic WaypointStrategic Waypoint

✈ A waypoint in the terminal area which is:A waypoint in the terminal area which is:✈Of such significance to the ATS provider that it must be Of such significance to the ATS provider that it must be

easily remembered and stand out on any display, oreasily remembered and stand out on any display, or✈Used as an ‘activation point’ to generate a message Used as an ‘activation point’ to generate a message

between computer systems when an aircraft passes it.between computer systems when an aircraft passes it.✈ Strategic waypoints are identified with 5LNCs unless they Strategic waypoints are identified with 5LNCs unless they

are co-located with a navaid, when the 3 letter navaid ID are co-located with a navaid, when the 3 letter navaid ID is used.is used.

✈ A waypoint in the terminal area which is:A waypoint in the terminal area which is:✈Of such significance to the ATS provider that it must be Of such significance to the ATS provider that it must be

easily remembered and stand out on any display, oreasily remembered and stand out on any display, or✈Used as an ‘activation point’ to generate a message Used as an ‘activation point’ to generate a message

between computer systems when an aircraft passes it.between computer systems when an aircraft passes it.✈ Strategic waypoints are identified with 5LNCs unless they Strategic waypoints are identified with 5LNCs unless they

are co-located with a navaid, when the 3 letter navaid ID are co-located with a navaid, when the 3 letter navaid ID is used.is used.

43

Page 44: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

Tactical WaypointTactical Waypoint

✈ Tactical: a waypoint which is defined solely for use in the Tactical: a waypoint which is defined solely for use in the specific terminal area and has not been designated a specific terminal area and has not been designated a strategic waypoint. strategic waypoint.

✈ Identified as Identified as AAAAXXNNNN, where:, where:

✈AAAA - the last two characters of the aerodrome location - the last two characters of the aerodrome location indicator; indicator;

✈XX - a numeric code from - a numeric code from 33 to to 99 ( (NN,, E E, , WW and and SS may be may be used instead if a State has a requirement for used instead if a State has a requirement for quadrantal information)quadrantal information)

✈NNNN - a numeric code from - a numeric code from 0000 to to 9999..

✈ Tactical: a waypoint which is defined solely for use in the Tactical: a waypoint which is defined solely for use in the specific terminal area and has not been designated a specific terminal area and has not been designated a strategic waypoint. strategic waypoint.

✈ Identified as Identified as AAAAXXNNNN, where:, where:

✈AAAA - the last two characters of the aerodrome location - the last two characters of the aerodrome location indicator; indicator;

✈XX - a numeric code from - a numeric code from 33 to to 99 ( (NN,, E E, , WW and and SS may be may be used instead if a State has a requirement for used instead if a State has a requirement for quadrantal information)quadrantal information)

✈NNNN - a numeric code from - a numeric code from 0000 to to 9999..

44

Page 45: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

RNAV Procedure IdentificationRNAV Procedure IdentificationNaming ConventionsNaming Conventions

RNAV Procedure IdentificationRNAV Procedure IdentificationNaming ConventionsNaming Conventions

✈““RNAVRNAV(GNSS) (GNSS) RWY 23” - is RNP approachRWY 23” - is RNP approach

✈““RNAVRNAV(RNP) (RNP) RWY 23” - is RNP-AR approachRWY 23” - is RNP-AR approach

✈““RNAVRNAV(GNSS) (GNSS) RWY 23” - is RNP approachRWY 23” - is RNP approach

✈““RNAVRNAV(RNP) (RNP) RWY 23” - is RNP-AR approachRWY 23” - is RNP-AR approach

4545

*ICAO State Letter SP 65/4-13/24, proposed change 1 DEC 2022 to:RNP and RNP(AR)

Page 46: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

Charting Altitude RestrictionsCharting Altitude RestrictionsCharting Altitude RestrictionsCharting Altitude Restrictions

4646

An altitude window : An altitude window : FL220 FL220 10,00010,000

An “at or below” altitude :An “at or below” altitude : 5000 5000

A “hard” altitude :A “hard” altitude : 30003000

An “at or above” altitude:An “at or above” altitude: 70007000

Page 47: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

FMS/RNAV limitationsFMS/RNAV limitationsFMS/RNAV limitationsFMS/RNAV limitations

✈Airspace Designers often want STARS to a Airspace Designers often want STARS to a metering fix and additional STARs to join to metering fix and additional STARs to join to initial approach Fix for each runwayinitial approach Fix for each runway

✈Cannot have two STARs in same flight plan in Cannot have two STARs in same flight plan in FMSFMS

✈Airway and approach transitions neededAirway and approach transitions needed

✈Airspace Designers often want STARS to a Airspace Designers often want STARS to a metering fix and additional STARs to join to metering fix and additional STARs to join to initial approach Fix for each runwayinitial approach Fix for each runway

✈Cannot have two STARs in same flight plan in Cannot have two STARs in same flight plan in FMSFMS

✈Airway and approach transitions neededAirway and approach transitions needed

4747

Page 48: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

Implementation/1 Implementation/1

48

✈Implementation decision✈PRE IMPLEMENTATION REVIEW!!!!

✈ATC system consideration✈TRAINING✈AIRAC cycle

Page 49: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

Implementation/2Implementation/2Implementation/2Implementation/2

✈Monitor processMonitor process

✈ Support OPSSupport OPS

✈Redundancy or contingency proceduresRedundancy or contingency procedures

✈ Support controllers and pilotsSupport controllers and pilots

✈Maintain logMaintain log

✈ Post Implementation Safety AssessmentPost Implementation Safety Assessment

✈Monitor processMonitor process

✈ Support OPSSupport OPS

✈Redundancy or contingency proceduresRedundancy or contingency procedures

✈ Support controllers and pilotsSupport controllers and pilots

✈Maintain logMaintain log

✈ Post Implementation Safety AssessmentPost Implementation Safety Assessment

4949

Page 50: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

Post ImplementationPost ImplementationPost ImplementationPost Implementation

✈Safety AssessmentSafety Assessment

✈ Have objectives been metHave objectives been met

✈ Have any safety issues been identifiedHave any safety issues been identified

✈ What improvements could be madeWhat improvements could be made

✈ Is there a continuing quality processIs there a continuing quality process

✈Safety AssessmentSafety Assessment

✈ Have objectives been metHave objectives been met

✈ Have any safety issues been identifiedHave any safety issues been identified

✈ What improvements could be madeWhat improvements could be made

✈ Is there a continuing quality processIs there a continuing quality process

5050

Page 51: VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014

Questions??Questions??Questions??Questions??

5151