Loading...
HomeMy Public PortalAboutFAA-BLOCK-1-Briefing-16 Oct 2018 4°�PPA ,q52,1 Federal o N Aviation 2 ra Administration National Air Traffic BOS ' Controllers Association BLOCK 1 Full Work GroupResponse Presentation to: Massport CAC By: Ken Brissenden, FAA ESA OSG Vicki Turner, FAA PBN Co-Lead Joseph Tinsley, NATCA PBN Co-Lead Date: October 18, 2018 The concepts in this presentation do not constitute, or imply, a reopening of the Boston Logan Airport Noise Study (BLANS) Any designs identified for further development must go through the environmental process VAOVV j)Id We Get Here? ❖ An MOU was signed between Massport and FAA September, 2016 ❖ Formation of 7100.41A PBN Full Working Group (FWG) ➢ May, 2018 FAA formed PBN FWG via FAA Order 7100.41 A ➢ FWG consists of Industry, Air Traffic Facilities, and Massport/MIT ➢ Reviewed BOS BLOCK 1 recommendations to determine operational feasibility ➢ Designed procedures in an attempt to mitigate BOS BLOCK 1 concerns and address FAA procedural requirements FAA JO 71 00 .41 A The Performance Based Navigation (PBN) Implementation Process Performance Based Navigation (PBN) Procedures ➢ Area Navigation (RNAV) Procedures o RNAV SIDS o RNAV STARS o Q and Y Routes o T Routes o TK Routes ➢ Required Navigation Performance (RNP) Procedures o RNAV RNP Approaches o RNAV RNP SIDs PBN IMPLEMENTATION PROCESS Phase 1 : Preliminary Activities Phase 2 : Development Work Phase 3: Operational Preparation Phase 4: Implementation Phase 5: Post Implementation ❖ Environmental review runs concurrently with the PBN phases and is completed prior to implementation Phase 1 IFP Gateway AJV-5/FPT Proceed No BAR/CWG 1 i Proceed BAR Conduct Initial Initial AJV-14 Review � Decision Baseline Continue to Phase 2 Analysis Decision Go Do Not Proceed No Go C Initial Review Terminate Baseline Terminate J Form Analysis Report :•Justify Work :-Validate Need :-Validate Priority Compare with other Requests N C Phase 2 Non-concur Design PBN FWG PBN Routes/ Finalization& FWG Concur Continue to Establish Finalize/Submit FWG � � � Review PBN Distribution Phase 3 Procedures Consensus Package RAPT Review Aeronautical Information Distribution Services(AJV-5) Package Development Establish FWG Develop Procedure Designs Documents are Prepared and Distributed Industry Flight Simulations N C Phase 3 Not Complete Developmental and Operational Activities Aeronautical Information Services(AJV-5)Development Implementation Planning Confirm Verify operational Complete Continue to Compliance Activities Industry Preparations Representative Activities p S Phase 4 Complete Notification and Training Automation Implementation Note:Activities shown may occur concurrently Strategy Plan ❖ Designs are: ❖ Air Traffic: ❖ Industry: ➢ Finalized ➢ Develops and Administers Training ➢ Develops and Administers Training ➢ Evaluated for Safety ➢ Develops Standard Operating Procedures (SOPS) ➢ Adapts Flight Plan Filing Automation ➢ Flight Checked ➢ Adapts Automation Software ➢ Sent for Publication Phase 4 No Review Operational Confirm yes Publish and Implement Continue to Preparations Complete S Routes/Procedures S Phase 5 Publish Procedures Implement Procedures Phase 5 Implementation Identify No Conduct Post- Submit to Project Monitoring Implementation Issues Implementation AJV-14 Complete Analysis Yes Determine Mitigations/ Post Resolve Issues Implementation Analysis Report :-Validate Procedure is Working Properly Identify and Mitigate Issues BOS Block 1 Status Update Block 1 Final Recommendations Proc. ID Procedure Primary Benefits D = Dep. A = Arr. 1-D1 Restrict target climb speed for Reduced airframe and total noise jet departures from Runways during climb below 10,000 ft (beyond 33L and 27 to 220 knots or immediate airport vicinity) minimum safe airspeed in clean configuration, whichever is higher. i 1-132 Modify RNAV SID from Runway Departure flight paths moved north 115R to move tracks further to away from Hull the north away from populated areas. 1-D3 Modify RNAV SID from Runway Departure flight paths moved north 22L and 22R to initiate turns away from Hull and South Boston sooner after takeoff and move tracks further to the north away from populated areas. 1-D3a Option A: Climb to intercept course (VI-CF) procedure 1-D3b Option B: Climb to altitude, then direct (VA-DF) procedure 1-D3c Option C: Heading-based procedure 1-A1 Implement an overwater RNAV Arrival flight paths moved overwater approach procedure with RNP instead of over the Hull peninsula and overlay to Runway 33L that points further south follows the ground track of the jetBlue RNAV Visual procedure as closely as possible. 1-Ala Option A: Published instrument approach procedure 1-A1 b Option B: Public distribution of RNAV Visual procedure .®�• N111�C (1 -D1 ) Restrict target climb speed for jet departures from Runways 33L and 27 to 220 knots or minimum safe airspeed in clean configuration, whichever is higher Primary Benefit: Reduced airframe and total noise during climb below 10,000 ft. (beyond immediate airport vicinity) ❖ A separate Work Group has been identified as this recommendation falls outside the scope of the PBN Implementation Process ❑ Work Group is composed of the following FAA Lines of Business ➢ Flight Standards ➢ System Operations ➢ Operations Support Group ➢ Air Traffic Control ➢ Office of Environment and Energy (AEE) (1 -D2) Modify RNA SID from Runway 15R to move tracks further to the north away from populated areas. Primary Benefit: Departure flight paths moved north away from Hull Notional design by Full Work Group as Design recommended by MIT of October 4, 2018 BRRRO WP266 y, FP.'OrX�X�X.�� Ir• � M[ilT' b Current Procedure Notional Procedure RWY 15R Transition (TXN) current and notional designs with recent radar tracks Winthrop - KBOS r"'BRR D- ' 1 tc r-;f- ♦ ��r -- ,1 l 11� Current Procedure - Notional Procedure WP266 is located approximately 1 .58 nm east of FOXXX 6 Radar tracks August, 2018 (1 -D2) ' ' ll Population E • • Lf Flight Tracks 8.LAMAX Noise Contours�dB] (LA,MAX) JJ 1 nm Spacing Marker Diff Baseline Flight Track Baseline AEDT B738 Contours — — —Alternate Flight Track Alternate AEDT 6738 Contours • Population benefited � Population No Change l� Population Dis6enefited t \' 1 RNAV 23 nmi Hin�f�am ��ha�set 0 o*H/STR (1 -D3) Modify RNA SID from Runway 22L and 22R to initiate turns sooner after takeoff and move tracks further to the north away from populated areas Primary Benefit: Departure flight paths moved north away from Hull and South Boston Option A: Climb to intercept course (VI-CF) procedure Option B: Climb to altitude, then direct (VA-DF) procedure Option C: Heading-based procedure (1 -D3a) Option A: Climb to intercept course (VI-CF) procedure - •'• RWY 27 arrival separation ° requirements keep RWY22 • �FRRO transitions from moving ='°�` further north F4xxx •'• Unable to move track further � aAirE from HULL Cfh4DH �+ T pop ux ❖ Shoreline crossing north of j "'" HEWMO would be at lower altitude x�� ❖ Original designs were not flyable t ❖ n h Currentdesig designs e Current Procedure sF,. result of extensive study by Notional Procedure industry and the FAA with the intent to be as far away from Hull as possible FWARDO After extensive review by the FWG, no further design t _ �- changes are feasible (1 -D3b) Option B: Climb to altitude, then direct (VA-DF) procedure Aircraft navigational limitations resulted in termination of the earlier VA-DF procedure in 2011 ❑ 2011 MITRE study confirmed aircraft navigational limitations ❑ Meetings with Industry resulted in recommendation of VI-CF procedures ❑ VI-CF procedures were developed and currently in use Wide splay of aircraft tracks were rejected by community ❑ There were numerous community complaints from South Boston and Hull that aircraft were too close/overflying the communities ❑ 2011 HMMH study commissioned by Massport confirmed wide splay of aircraft tracks; Recommended VI-CF procedures to correct ❑ VI-CF procedures were developed and currently in use The current Work Group reviewed the VA-DF option and determined Runway heading to 520ft prior to turning to the first waypoint is not feasible ❑ Would cause heavy/low performing aircraft to fly over Hull due to delayed turns because of slower climb rates (1 -D3c) Option C: Heading-based procedure ❖ Increases verbiage between Local Control, Departure Control and pilots ❖ Increases probability of readback/hearback errors, a safety issue ❖ Shortening departure paths cause conflicts with ROBUC STAR, particularly with heavy/low performing aircraft ❖ Current procedures from 4R, 9, 15R, 22R/22L provided noise benefits to shoreline communities ❖ Logan CAC requested RNAV SID departures in lieu of vector based procedures * Vector based procedures are in direct conflict with BLANS (BLANS Table 3-2) (1-Al) Implement an over water RNA approach procedure with RNP overlay to Runway 33L that follows the ground track of the JetBlue RNA Visual procedure as closely as possible Primary Benefit: Arrival flight paths moved over water instead of over the Hull peninsula and points further south * The following designs are intended for use when operational conditions allow, primarily when Nocturnal Procedures are in use during periods of very low traffic volume NOCTURNAL STARs OBJECTIVE - Mirror the ROBUC, JFUND and OOSHN RNAV STARs with runway transitions that connect to RNAV approaches developed during evaluation of the Block 1 recommendations New Nocturnal STARs ❑ LUNAA (RNAV) STAR (mirrors ROBUC) ❑ BUNNT (RNAV) STAR (mirrors JFUND) ❑ CGURL (RNAV) STAR (mirrors OOSHN) Notional RNAV (RNP) RWY33L �exlRq t4R wincrwftrr AlqT.O$! MedfOrd. f 1r,` I _ tj III I �ArlinUtV" x;Rcwfrd III Nit �amtrwrlle '{h•lsea " Iltlravn CamUrid�F wuijhralt 'IjW21,� W at�rtPWrF{ KBQ UU' • '�o�x �.. '�' �13 ' Y8.'r1r�kE-lJ 30(�0 4000 Me6*61 Brookline Y'+ 5' '1Fw1 WP996 VJFd?� PF �v ''CUU %lull IYdrYM� 9.1 IPg2r ■ VI�{�+ M [lrtihvt� Alilton Hingham. ,Cohassk YYemQ+rth North Su4uatr B ray ntre e{ Narwtkad• S[ItU41W u�Ol �diYdt��i�+ :••�. Nax�� ' tintrin Fid '4c�i ,k rr PAarahlldtl Eln I x 11. Shrfron SGau�ltitrif�` . -IsiS.�ti�F_ Abogtoit. RNAV (RNP) RWY33L with RNAV VISUAL (Stoneham .Swam pscott Saugus EY !?r rester M el rose VVP308 VVP307 I's tMaiden I Everett Revere, 1 RNAV(RNP)-Blue k,5 o m ervtl ; Jetble RNAV Visual-Red VVP306 CIS el sea ' t Wiry throe r KBO M Emard Lawrence VVP 18 `Bost -rai kntl Mrpors VVP213 YAVVKE- PFAF5 VVP52 WORRN `Hull 4, NoiseMIT Notional Design RlIMht TR9T i L-rr-X N."- Population Exposu re L��� 1 rrn$parJr�IWarftar �rtsaliro�E�T����nher.irs -�lornoM10 FlFght Trams �k�rneXF6�Drr 6T3�C�4rYb+�e w ;� Pv lahxt 6�� pe�j '�B4#1 N4 GrdrrrQrE �aaa,lerLRled d. �li�ngh.�m h�ss�t Wo RPL aVI,/fo 0 o;H/STR RNAV (GPS) RWY 33L Recommendations RNAV (GPS) RWY 33L - Introduction ❖ Development tasked to overlay to the extent possible JetBlue RNAV Visual Rwy 33L Approach ❖ OSG-FPT has designed 7 designated versions of the procedure ❖ All 7 had issues identified by either Industry, CAC or failed safety criteria RNAV (GPS) RWY 33L Approach (version 1 ) ❖ Industry Concerns ❑ Airlines expressed concern that an offset final to runway 33L can cause confusion to pilots. Pilots may assume approach runway 32 thinking that it is runway 33L during night hours ❑ Being in a turn at low altitude when turning to final approach ❑ Reflections off water at night which could cause confusion for the pilot RNAV (GPS) RWY 33L Approach (version 3) ❖ Procedure was developed and flight inspected ❖ Flight Standards office approved a waiver to allow the use of a 39' turn on final for this procedure ❖ Was reviewed by Massport and Community Advisory Committee ❖ Modifications currently being reviewed by Industry * Industry expressed that they will be unwilling to fly turns greater than the 390 in the final phase of flight, the maximum allowed ❖ Prior to publication of the procedure, Massport and CAC asked the FAA to move route further from Hull RNAV (GPS) RWY 33L Approach (version 2,4,5) ❖ Version 2,4,& 5: Concept of a straight-in final approach segment based on an initial segment that overflies the Nahant Causeway — while maintaining additional lateral separation from Hull ❖ Concepts included various final approach fix altitudes, segment lengths, and descent gradients greater than safety standards allow RNAV (GPS) RWY 33L Approach Versions 6 and 7 ❖ Both version were proposed by Industry during collaborative Work Group meetings ❖ Were attempts to mimic Jet Blue Special RNAV Visual while meeting safety standards for RNAV GPS public procedures ❖ The tracks moved close to or over Hull (version 6) ❖ Moving the tracks created safety issues with obstructions (version 7) Traffic Flow Implications Use of RNP RWY33L will be limited when all traffic is not able to accept clearance RNP RWY 33L and ILS RWY 33L are not able to be used simultaneously due to dissimilar tracks and lack of sequencing tool RNP RYW33L and GPS RWY 33L can be used simultaneously due to similarity of track paths RNAV (GPS) RWY 33L (version 3) Stoneham ,Swamp5cott :. 'Saugus EYr�nVVP192 rester el rose 6000 210K 7000 210K , ,.1 �4800 I, IM-aIclen 1 Everett Revere. omerville ' helsea dodo th Winro . NP429 KBO VVP432 'Bost 6000 2900 000 f 4000 WPd28 WP11 2200 210K VIP3'S PFAF2 v9 2 1000 1600 `Hull VVP427 6_ 000 RNAV (GPS) RWY 33L With RNAV Visual Stoneham Ly qn,. Swam pscott Saugus VVP192 rester Melrose 6000 210K 70 VVP561�A800 I. (Malden 1 E v erett R ev ere. RNAV(GPS)-Green ,Somerville 'Chelsea JetbleRNAVVisual-Red AM 4000 ' Winthrop vvP429 WP560 KBO WP432 "Bost 6000 YAWKE- 2900 4000 ;? 000 WP428 11 W00 210K WP315 WOP 1600 FAF2'v3 2 1000 - "Hull .. 000 RNP RWY 33L and GPS RWY 33L -Saucju5 Winchester M elrose 6000 210K 7000 210K 4800 ldfordf *Malden ngton Everett Revere, RNAV(RNP)-Blue r 0"I"rVllle *Chelsea GPS Y Ver.3.2-Green 4000 3rid�e Win throp KBO r4 EOw ird Lawrence «Bost -zo;;11 Arlon 6000 2900 4000 -line' 3000 _ 0 210K 1000 160C Null r �•. 000 SQuincy Milton Hingham. , 011asset r RNP RWY 33L and GPS RWY 33L with RNAV Visual *Saugus LY III I .. .,. , Winchester M el rose--.4. 6000 210K 7 r dford* *Malden ngton Everett Revere, RNAV(RNP)-Blue # 04 vllle *Chelsea GPS Y Ver.3.2-Green 4000 ridge Wi rs throp Jetblue RNAV Visual-Red KBO 'Bost Al 4111 n ^ 6000 ; 2900 4000 3000 line, 0 210K 1000 1600 Hull 000 Quincy Milton Hingham, �ohasset t (1 -Al b) Option B: Public distribution of RNA Visual procedure The recommendation will be resolved by (1 -A1 ) 0