Summary of the First Meeting Special Committee 227 ... - RTCA

More documents

Recommendations

Info

SBAS is here, GBAS and new constellations are coming Future of SC227 We need to fix the broken pieces, at least the ones that matter o Cert remains painful o Radio nav and integrity issues need to be closed out o Availability vs. integrity o CDI/VDI display issues need resolution, including dual aspects o Classic procedures in an RNP flight deck o Offsets, RNP holds, fixed radius turns o Temp comp – debate about what to do here o Users need better information presented… pilots, controllers o Charts/FMS/Database harmonization • RNP minima vs. RNP by leg, RNP by leg not on the chart o MOPS need to be tightened up in support of TSO C-115c We need to refine the features with value and try to jettison the rest Time constrained waypoints o Performance requirements – keep it simple – what matters Don’t forget security – it’s coming Related functions – FMS is the info hub of the flight deck Wednesday, 3/7 FMS Standardization – Mike Cramer Mike Cramer, MITRE Mike also leads the FMS Standardization working group (of the CNS task force), that led to a number of ATA task force recommendations. FMS Standardization Issue, FMS Runway Alert, dated Dec 8, 2011 Ref: “FMS Standardization - Runway Alert Recommendation Final.pdf” This paper attempts to describe from the user/ATC side, the issue of departure operations from the wrong runway, differences in system detection methods and alerts, and the needed for improved/new solutions. Main recommendation: The FMF should identify and alert pilots of a discrepancy between loaded and actual departure runway when takeoff power is added. FMS Standardization Issue #27 Speed and Altitude constraints Ref: “FMS Standardization Spd Alt Constraints Recommendation Final.pdf” This paper points out that constraints are not handled the same in different systems. Some can be worked around with procedure changes to account for the differences. Speed-only constraints require ‘fake’ altitude constraints on some systems. Some procedures need AT or At-or-Above speed constraints, and the FMSs aren’t designed for this. Sequencing of speed and altitude constraints differ on some systems – sequencing either the altitude or speed can cause early sequence of the other. Recommendations: 1. speed-only constraints should be allowed on FMSs. 2. when associated with an altitude constraint, the speed constraint should remain active until the waypoint is sequenced or deleted. 3. FMSs should provide auto-throttle or appropriate commands so that airspace does not deviate more than 10 knots (0.02 Mach) 4. FMSs should support all four types of speed constraints (at, at/below, at/above, between) 12
Q: what is the impact on economy of flight with these speed constraint changes Mike: There is 3D-PAM study on this. If procedure is done well there is not much impact. Issue Lateral Offset Operation Ref: “FMS Standardization of Lateral Offset Operation FINAL RECOMMENDATION.pdf and FMS Standardization - Lateral Offset and FRT.pdf” The first paper indicates that FMS treatment of lateral offsets differ to the point that ATC cannot easily use it as a tool. Entry and exit treated as a straight path, but the intercept angle varies between 30 and 45 degrees, but some aircraft allow specification of the angle in the AMI and some systems allow the pilot to enter the angle. Most perform a flyby transition from parent path to intercept path. Some systems display offset path and intercept track, others don’t. Some systems allow 0.1nm increments, others only 1.0nm. Some systems allow specification of the lateral offset start and end points, some don’t – they only allow immediate engagement and disengagement of the offset. This variation makes it difficult for ATC to use it because the result of the clearance varies. ATC use of this is desired, and ATC automation tools are being developed that could make use of this capability if its response were consistent. Desired operations: 1. all aircraft should respond in a consistent and predicable manner to lateral offset clearances. 2. all aircraft should be capable of offsets up to 99nm in 0.1nm increments. 3. offset types should handle optional specification of begin and end fixes. Recommendations: 1. intercept angle default is 30 degrees. 2. flight deck selectable intercept angle from 10-50 degrees to use as needed 3. start and end waypoints should be specifiable a. automatic initiation and cessation at these points b. the intercepts should be flown with fly-by transitions 4. offset distances specifiable by 0.1nm 5. common requirement for which ARINC path terminator types that should be offsetable. a. Fixed radius transitions should be preserved for the offset by offsetting the turn center along the bisector b. For RF path terminators the radius should be changed by the amount of the offset 6. terminators that automatically terminate a. no system should allow offsets to be applied in approach or missed approach segments i. offsets should automatically terminate at first approach waypoint ii. do not propagate across route discontinuities or unreasonable geometries. 7. provide data to support the map display 8. do not need to support multiple pre-planned offsets 9. provide output of intent on ADS-B and ADS-C A table of current behavior across different FMSs was also presented in the second paper. From a timetable standpoint, ATC automation tools will start coming along around 2015. Frank: concern about lateral offset terminating at FAF. Mark: a clearance like this should not be issued. There was general agreement that it should still be fixed in the document 13
Page 1 and 2: Summary of the First Meeting Specia
Page 3 and 4: NEXTGEN IMPLEMENTATION PLAN (NGIP)
Page 5 and 6: NextGen Implementation Plan (NGIP)
Page 7 and 8: • flight deck display of speed cu
Page 9 and 10: Powerpoint: “3a Standards of Navi
Page 11: Sharing of common flight plan betwe
Page 15 and 16: Section 1.1 para 3 is significant.
Page 17 and 18: David DS: network and flow manageme
Page 19 and 20: concern that we don’t have moment
Page 21: Prioritization and Scope of Updates

Summary of the First Meeting Special Committee 227 ... - RTCA

Create successful ePaper yourself

Delete template?

Save as template?