The Fighter Data Link (FDL), integrated into USAF and Air National Guard (ANG) F-15 fighters, provides improved situational awareness and sensor cueing in support of air superiority and interdiction missions. The FDL provides Link 16 data link networking with other Link 16 capable aircraft, command, and control systems. The FDL shares a number of components with the Multifunctional Information Distribution System (MIDS) terminal.

The FDL was developed independently, but under the umbrella of the MIDS program and shares 30 percent commonality with MIDS. The FDL was designed to satisfy the USAF's "Urgent Need" for Link 16 data link in the F-15 fighter. The overall MIDS architecture is modular and additional capabilities, such as digital voice and imagery exchange can be inserted if required. The host platforms for the FDL are the ANG F-15A/B and USAF F-15C/D/E fighters. Initial Operational Test and Evaluation (IOT&E) was completed in FY00 and an Follow-On Test and Evaluation (FOT&E) was completed in FY01. The FDL was found to be operationally effective and suitable and it has been fielded to operational squadrons.

DOT&E encouraged increased information sharing and test support by FDL developers, users, and testers with the F-16 and F/A-18 MIDS integration efforts. This included lessons learned exchanges, technical advice regarding Link 16 integration, test design, and participation in test events. The F-15 FDL supported Navy F/A-18 MIDS and MIDS on Ships developmental test (DT) events.

The one-year FOT&E ended in 2001. Its focus was reliability, integrated diagnostics Built-In Test (BIT), and logistics supportability.

The USAF has a requirement for 1,000-hour Mean Time Between Critical Failure (MTBCF) for the FDL. The FOT&E result is 963 hours MTBCF. While falling short of the 1000-hour requirement, the reliability exceeds the predecessor F-15 Class 2 Joint Tactical Information Distribution System reliability findings by approximately 400 percent. The BIT evaluation indicated that the F-15 Operational Flight Program (OFP) 3M is not suitable due to excessive False Alarms. OFP 4, planned for fielding in FY02, will provide a method for post-flight BIT data retrieval and the laboratory test OFP 4 with the enhanced BIT indicated a zero percent false alarm rate. Logistics supportability met the USAF specification, however AFOTEC has recommended increasing spares to allow for shipping delays to and from overseas deployment locations. This could add to FDL life-cycle costs. There were also deficiencies with the Interference Blanking System cable design and battery.

FDL-equipped F-15 aircraft supported F/A-18 MIDS-LVT-1 DT through participation in a common Link 16 network. While the F-15 FDL was generally interoperable on the Link 16 network with other Link 16 capable systems, there were F-15 FDL to F/A-18 MIDS message interoperability issues. This included difficulty in sharing engagement status and target contact information through Link 16 messages.

The F-15 FDL and F/A-18 MIDS fighter-to-fighter interoperability issues are a concern, particularly when Joint interoperability certifications have already been granted. OSD and Joint Staff Link 16 sponsors should review the deficiencies discovered, update message implementation standards if needed, and assign responsibility for correction. A joint operational verification test of both development and fielded legacy Link 16 host platforms is needed.

Lessons from F-15 FDL integration have proven valuable and have positively aided other MIDS integration efforts. All Service data link programs should be more aggressive in ensuring information is distributed to the Link 16 community and that a common problem resolution data base is created.