Defense

December 19, 2012

New F-16 software platform to be tested by 40th, 85th

Tags:
Samuel King, Jr.
Eglin AFB, Fla.


Developmental testing for an F-16 operational flight program will be accomplished at the 40th Flight Test Squadron and 85th Test and Evaluation Squadron at Eglin Air Force Base, Fla., for the first time.

The testing for Block 40 and 50 model F-16s is scheduled to begin in 2014 and will also be the first time developmental testing and operational testing of the OFP will be conducted at the same base.

“This not only gives DT and OT pilots the unique opportunity for daily face-to-face contact to discuss potential test issues, but also allows OT pilots to participate in DT missions alongside their counterparts,” said Beau Booth, the F-16 M7 OFP project specialist for the 40th Flight Test Squadron.

An OFP is the software in the F-16 that controls the avionics and allows the jet to interface with external weapons. It is currently in the design-try-out phase here. This phase is primarily to help the software developers.

“In the DTO phase, a few early versions of the software, with limited subsets of the planned new capabilities, are flight-tested to ensure basic functionality so the software engineers can easily make any fundamental changes before they get too far into the coding,” said Booth.

This takes on a greater importance with this new OFP because it’s the first time an Air Force unit has developed the software. Previous F-16 OFP updates were created by Lockheed-Martin, but the 309th Software Maintenance Group from Hill Air Force Base, Utah, is the developer for this iteration.

Previous DTO phases had a limited number of sorties due to resources and test objectives.

“While this approach is adequate, it results in a relatively small number of opportunities to find potential errors,” said Booth. “Since there are multiple ways to execute most tasks in the F-16, there are a lot of potential combinations of pilot actions. DT does not have the resources to test.”

This was not the case with this DTO phase, however, since both OT and DT pilots were available to participate. To date, the combined test team has flown 41 test sorties. The previous F-16 OFP DTO included only 13 test sorties

“The ability to conduct a fully integrated DT/OT test program allows us to test new OFPs more thoroughly and field them faster and cheaper than ever before,” said Booth.

Historically, even though an OFP passes DT, OT pilots would find new software errors due to the amount of flight time and pilot availability. The added use of OT resources increases the potential of finding anomalies in the software. It also gives OT pilots, who are ultimately responsible for the final fielding recommendation, a chance to evaluate the software development early. OT’s upfront involvement cuts down on any late software changes. It also avoids the associated extra test requirements, increased costs and fielding delays that could happen.

Although this F-16 OFP partnership is a new endeavor for the squadrons, the 40th and 85th are frequent collaborators in developmental and operational testing. They are even headquartered in the same building for additional functionality.

“In these fiscally constrained times, the 40th and 85th are setting the benchmark on how to perform integrated test,” said Lt. Col. Thomas Seymour, the 85th TES commander. “Being collocated is the key. This allows us to share aircraft, infrastructure, aircrew and ideas, which results in more effective and efficient test and a better end product for the warfighter.”

This new software package will be incorporated in all active-duty F-16s and many Reserve aircraft.




All of this week's top headlines to your email every Friday.


 
 

 

Headlines January 28, 2015

News: Panel will propose new military retirement system - The long-awaited report on military compensation set to drop Thursday will propose fundamental changes to military retirement and health care benefits, according to several people familiar with the report. Source: DOD to request $585 billion for fiscal 2016 - The Department of Defense is preparing to submit a...
 
 

News Briefs January 28, 2015

Defense contractor to pay $2 million to settle claims A Northern California defense contractor will pay the federal government $2 million to settle claims about its manufacturing of parts for remote-controlled aircraft. The U.S. Attorney’s Office in Sacramento says Sacramento-based Composite Engineering Inc. agreed to pay the money to end allegations that it artificially inflated...
 
 
Navy photograph

USS Roosevelt marks 200,000 trap

Navy photograph An F/A-18F Super Hornet flown by Capt. Daniel Grieco, commanding officer of the aircraft carrier USS Theodore Roosevelt (CVN 71), and Capt. Benjamin Hewlett, deputy commander of Carrier Air Wing (CVW) 1, complet...
 

 
Navy photograph by PO1 William Larned

USS California returns from maiden deployment

Navy photograph by PO1 William Larned The Virginia-class attack submarine USS California (SSN 781) returns from its maiden deployment to its homeport at Naval Submarine Base New London. Under the command of Cmdr. Shawn Huey, Ca...
 
 
Army photograph

Army proves new watercraft capabilities

Army photograph Marine Corps assets are loaded onto the USNS Sgt. Matej Kocak (T-AK 3005), from an U.S. Army Landing Craft Utility, or LCU, USAV Port Hudson during port operations, at White Beach Naval Base, Jan. 22, 2015. Sold...
 
 

Orbital stockholders approve merger with ATK’s aerospace, defense groups

Orbital Sciences Corporation announced Jan. 27 that at a special meeting, the company’s stockholders voted overwhelmingly to approve the proposed merger with the Aerospace and Defense Groups of Alliant Techsystems Inc., pursuant to the definitive transaction agreement dated April 28, 2014. Approximately 99 percent of the votes cast at the special meeting voted in favor...
 




0 Comments


Be the first to comment!


Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>