Find Articles in:
All
Business
Reference
Technology
News
Lifestyle

Who's afraid of MFOQA

Mech, Fall, 2003 by Dan Steber

I imagine some readers may be afraid of MFOQA simply because it's another acronym and they don't know what the heck it is. Don't worry, it's not the latest virus. Rather, it could reduce mishap rates and save lives.

What is MFOQA? Capt. Mike Williamson, program manager for NavAir's Air Combat Readiness program office said, "The Military Flight Operations Quality Assurance Program is a concept of operations that provides the warfighter with timely and quantitative information regarding aircrew and system performance."

In NavAir press release No. 0603-03-1103, Vicky Falcon wrote, "MFOQA began as an effort to more efficiently tap into the Navy's and Marine Corps' information-collection capability. Every naval-aviation platform currently gathers data-to varying degrees-but modern digital aircraft and recorder technology allows for collection of virtually all aircraft data. By developing the tools to take that raw data from the aircraft and deliver meaningful, manageable information, Capt. Williamson's team can give the fleet improved decision-making capabilities."

She added, "With MFOQA, Navy and Marine Corps leadership will be empowered to make assessments based on specific data. Training needs can be uncovered and targeted, and the ability to exploit strengths and minimize weakness can enhance operations. Most importantly, though, problems or risk areas can be identified and addressed prior to a mishap."

Capt. Williamson said, "My team has been working closely with the Deputy Assistant Secretary of the Navy for Safety (DASN-Safety) to proactively pursue improved operational capabilities-and safety is an intrinsic part of any unit's operational capability."

Ms. Falcon wrote, "Through the efforts of DASN (Safety), the focus on MFOQA as an initiative to decrease the human-error rate and reduce aircrew skill-based errors throughout the Department of Defense (DoD) aviation community has been elevated to the Secretary of Defense."

Connie DeWitte, Deputy Assistant Secretary of the Navy for Safety, said, "We view MFOQA as a critical new initiative that will potentially give naval aviation the tools required to break below the current plateau in aviation mishaps." She added, "Naval aviation has designed and incorporated a number of major improvements over the years that have resulted in significant and sustained reductions in our aviation-mishap rate."

I asked Kurt Garbow (a retired captain, and former CO of HM-14, air boss, XO on USS Inchon, and Deputy COMNAVSAFECEN on the OPNAV staff and now MS. DeWitte's Director of Aviation and Operational Safety) a question at the Naval Aviation Maintenance Safety Symposium about the hardware related to MFOQA. He repeatedly reminded me that MFOQA does not involve just putting another recording device on an aircraft. Although flight-data collection is a critical part, MFOQA is a process that collects, records and downloads aircraft and flight data for animation, analysis and dissemination after every flight. Mr. Garbow demonstrated a mini-QAR (quick access recorder-see the photo) that had been flown during a Navy e-Business MFOQA demonstration on an FA-18 belonging to VMFAT-101. Holding up the small cigarette-lighter-sized recorder, he said, "This equipment was a COTS item and validated the test, but it likely will not be the equipment of choice as a final solution on all aircraft types."

A few maintainers at the conference were concerned about the level of information available from flight-data recorders and were worried about the work that might be generated by "false positives." Mr. Garbow displayed a slide showing an aircraft that had recorded fuel-flow differences, with an excessive split. Only one pilot wrote a VIDS/MAF indicating a problem, but a review of the data revealed many other occurrences. One purpose of the MFOQA program is to display potential trends before a critical failure. In this case, the fuel-flow splits existed on a number of flights, but pilots had not noticed or documented them.

DASN(Safety) answered what Mr. Garbow referred to as a "snowflake" from the Secretary of Defense about mishap rates. Three items were seen as critical to achieve reduced rates: lowering human errors, increasing and improving simulators, and implementing MFOQA.

Mr. Garbow said, "The data-collection part of MFOQA would require a download of data after every flight and would provide quantitative information about the aircraft and the people who fly it." During the FA-18 MFOQA demo at VMFAT-101, he mentioned the download of data on the flight line took 30 seconds, with another 30 seconds required to upload the data to a standard PC. He then displayed slides showing how numerous flights could be automatically analyzed to review and identify trends. In one slide, ground speeds at touchdown were evaluated.

DoN-wide MFOQA demonstrations are strongly supported by OSD, and DASN(Safety) is waiting on funding to execute a comprehensive demonstration program involving a number of other aircraft. Mr. Garbow mentioned that MFOQA likely will not be developed for all aircraft in the fleet, but the advent of more advanced aircraft will make the process easier. He said some may need only a soft-ware change, while others may need an actual "install" of recording equipment.

 

BNET TalkbackShare your ideas and expertise on this topic

The following tags are supported in BNET comments:
<b></b> <i></i> <u></u> <pre></pre>

Leave a Reply

  1. You are currently a guest | Login?
advertisement
Go
advertisement
  • Click Here
  • Click Here
advertisement

Content provided in partnership with http://findarticles.com/source//