PMA209 2012 Core Avionics Master Plan - NAVAIR - U.S. Navy

More documents

Recommendations

Info

Core Avionics Master Plan 2012 Appendix A-52. Funded Enhancements and Potential Pursuits.Improved Operational Play-back and Assessment Tools - Military FlightOperations Quality Assurance (MFOQA). (2014) The commercial airline industryinstituted a Flying Operations Quality Assurance (FOQA) program to help withprocedural standardization and pilot proficiency. The major airlines reported that theprogram produced measurable improvements in aircrew proficiency and significantreductions in hazardous events. An OSD memorandum (dated 11 Oct 2005) forSecretaries of the Military Departments directed all Department of Defense (DoD)components to implement a multi-faceted MFOQA capability. Subsequently, theSecretary of the Navy issued a similar memorandum (dated 2 Feb 2006) to theCommandant of the Marine Corps and the Chief of Naval Operations supporting theMFOQA process.Military Flight Operations Quality Assurance (MFOQA) is a knowledge managementcapability and a software-based process that will be hosted on existing Department ofthe Navy (DON) Information Technology (IT) assets. MFOQA will collect, merge, andanalyze pre-recorded aircraft flight data and other available data, such as aircrewinformation, and make the results available to authorized users. MFOQA is a riskmitigation tool which will provide a proactive approach to identify human errors andfailing material components so corrective actions can be taken prior to an aircraftmishap or costly maintenance failure. Changes in flight procedures, habit patterns,training methods, and maintenance practices based upon MFOQA analysis have thepotential to reduce the flight mishap rate and increase readiness.Whereas ORM is a proactive and subjective process based on operator analysis ofpotential risks and implementation of risk mitigation strategies, MFOQA objectivelyanalyzes actual performance data. It involves rigorous post-flight off-aircraft analysis ofdata downloaded after every flight. MFOQA supports four primary functional purposes: Flight Data Analysis (FDA): Automated computer analyses of every flight toidentify hazardous events and trends before mishaps occur, or events and trends ofuser interest, which can be presented to an authorized user in the form of automated,tailorable reports highlighting significant events or sampling multi-flight aggregate datafor trend analysis. Post-Mission Aircrew Debrief (PMAD): Post-flight digital replay and automatedreport generation for any portion of a flight presented to an authorized aircrew toenhance aircrew training. Aircraft Maintenance and Trouble-Shooting (AMATS): Quantitative downloadedaircraft system information presented to an authorized aircraft maintenance user toassist in maintenance and to improve the operational readiness of aircraft. Mishap Investigation (MI): When aircraft flight data is not destroyed in a mishap,the aggregation of PMAD, AMATS and FDA analyses capabilities can provide muchimproved and objective evidence to the Aviation Mishap Board (AMB) to identify causalfactors for remediation of flight and ground mishaps.A-5 Flight Safety 8
Core Avionics Master Plan 2012 Appendix A-5These features permitting aircrew, maintainers and leadership to assessperformance, validate ORM strategies, and proactively implement changes toprocesses and procedures to improve future readiness, efficiency, and safety. Analysistools are available at the squadron level immediately after each flight, which can beapplied in the aggregate across all flight records stored in a file repository. MFOQA willaid in risk management and improve readiness across the spectrum of operations,including Maintenance, Operations, Safety and Training. The maintenance aspects ofMFOQA are designed to supplement current maintenance procedures and processes,and will not replace any established systems. The Navy MFOQA program is theapproved Enterprise program of record for Naval aircraft. The F/A-18C-F and EA-18Gare the lead platforms for integration of this capability.Autonomous Risk Identification. (2016) Software is being developed to analyzeaircraft data and automatically identify desired trend information. For MFOQA purposes,the goal would be to identify operational or proficiency trends that present potential risksor imminent mishaps. This tool would reduce manpower workload for instructors orsquadron analysts, and allow a higher level of analysis across dozens or hundreds ofsorties versus compilation of individual post-flight assessments. It could also enablehigher level commands, such as Wing commanders or Chief of Naval Air Training(CNATRA), to get automated risk identification on a larger scale across squadrons.Enterprise Level MFOQA. (2017) The first increment of MFOQA enables post-flightanalysis at the squadron level. MFOQA Increment 2 would incorporate enhancementsthat support multi-squadron and cross-platform reporting and trending analysis for abroader view of data trends across the Enterprise.Focused Operations Modules. (2017) With additional work, MFOQA analysis toolscould be developed to enable comparison of aircrew specific maneuvers performance to“gold standards.” Commander Naval Air Forces (CNAF) has expressed interest indeveloping modules to support Field Carrier Landing Practice (FCLP), strike, and autorotationevolutions to enhance Safety and Training. Analysis modules developed byCNAF would be adapted and integrated into the MFOQA program of record.Shipboard Recovery Animation. (2020) The current MFOQA program of recorddoes not include complex analysis and software development required to enable theability to visualize takeoffs or landings in the highly dynamic shipboard environment.MFOQA Increment 3 is planned to include enhancements that would incorporate shipposition and motion into the visualization module to enable accurate portrayal of a flightduring embarked operations.Classified MFOQA. (2020) Certain platform missions regularly involve utilization ordownload of classified information and/or capabilities. MFOQA Increment 3 would be aclassified variant of the Increment 2 baseline unclassified Enterprise level utility, and isintended to perform the same functional requirements.A-5 Flight Safety 9
Page 1 and 2:
PMA209Endorsement and DistributionP
Page 3 and 4:
Table of ContentsExecutive SummaryE
Page 5 and 6:
Core Avionics Master PlanExecutive
Page 7 and 8:
Core Avionics Master Plan Ensure th
Page 9 and 10:
I. INTRODUCTION.Core Avionics Maste
Page 11 and 12:
IV. RECOMMENDED PRACTICES.Core Avio
Page 13 and 14:
Core Avionics Master Plan2. Where p
Page 15 and 16:
Core Avionics Master Plan3. Leverag
Page 17 and 18:
Core Avionics Master PlanSECNAVISNT
Page 19 and 20:
Core Avionics Master PlanThe follow
Page 21 and 22:
Core Avionics Master PlanIn 2010, P
Page 23 and 24:
Core Avionics Master PlanDoD 4140.1
Page 25 and 26:
Core Avionics Master Plan 2012Appen
Page 27 and 28:
Core Avionics Master Plan 2012 Appe
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50: Core Avionics Master Plan 2012 Appe
Page 99: Core Avionics Master Plan 2012 Appe
show all

PMA209 2012 Core Avionics Master Plan - NAVAIR - U.S. Navy

Create successful ePaper yourself

Delete template?

Save as template?