F-111 Systems Engineering Case Study - Technical Details, Program History, Combat Operational History of Controversial Fighter-Attack Aircraft PDF Download
Are you looking for read ebook online? Search for your book and save it on your Kindle device, PC, phones or tablets. Download F-111 Systems Engineering Case Study - Technical Details, Program History, Combat Operational History of Controversial Fighter-Attack Aircraft PDF full book. Access full book title F-111 Systems Engineering Case Study - Technical Details, Program History, Combat Operational History of Controversial Fighter-Attack Aircraft by U. S. Military. Download full books in PDF and EPUB format.
Author: U. S. Military Publisher: ISBN: 9781549689314 Category : Languages : en Pages : 99
Book Description
This is one of a series of systems engineering case studies prepared by the Air Force Center for Systems Engineering. This case study analyzes the General Dynamics (GD) F-111, unarguably the most controversial fighter-attack aircraft ever developed. It suffered from a nearly impossible multi-role/multi-service requirement specification, and a protracted development cycle in which numerous serious technical problems had to be identified and corrected. Of the 1,726 total aircraft buy that had originally been planned in 1962, only 562 production models of seven different variants were completed when production ended in 1976. The systems engineering process and its application to the F-111 program from 1958 to 1976 will be examined through discussion of five fundamental systems engineering learning principles that were derived from research on the F-111 program and from interviews with key F-111 government and contractor managers. Through examination of these systems engineering learning principles, the reader will gain an appreciation of the circumstances in the F-111 program that had the most influence on the outcome of the program and the government and contractor personnel who managed the F-111 systems development. The study provides a wealth of technical information about the aircraft and its complex history. The Department of Defense is exponentially increasing the acquisition of joint complex systems that deliver needed capabilities demanded by our warfighter. Systems engineering is the technical and technical management process that focuses explicitly on delivering and sustaining robust, high-quality, affordable solutions. The Air Force leadership has collectively stated the need to mature a sound systems engineering process throughout the Air Force. Gaining an understanding of the past and distilling learning principles that are then shared with others through our formal education and practitioner support are critical to achieving continuous improvement. These cases support academic instruction on SE within military service academies, civilian and military graduate schools, industry continuing education programs, and those practicing SE in the field. Each of the case studies is comprised of elements of success as well as examples of SE decisions that, in hindsight, were not optimal. Both types of examples are useful for learning. Along with discovering historical facts, we have conducted key interviews with program managers and chief engineers, both within the government and those working for the various prime and subcontractors. From this information, we have concluded that the discipline needed to implement SE and the political and acquisition environment surrounding programs continue to challenge our ability to provide balanced technical solutions. FOREWORD * ACKNOWLEDGEMENTS * EXECUTIVE SUMMARY * 1.0 SYSTEMS ENGINEERING PRINCIPLES * 1.1 General Systems Engineering Process * 1.2 F-111 Major Learning Principles * 2.0 F-111 SYSTEM DESCRIPTION * 2.1 F-111 Characteristics * 3.0 F-111 SYSTEMS ENGINEERING PRINCIPLES * 3.1 Learning Principle 1 - Requirements Definition and Management * 3.2 Learning Principle 2 - Systems Architecture and Design Trade-Offs * 3.3 Learning Principle 3 - Communications and Systems Management * 3.4 Learning Principle 4 - Validation and Verification * 3.5 Learning Principle 5 - Program Management * 4.0 SUMMARY * 5.0 REFERENCES * 6.0 LIST OF APPENDICES * Appendix 1 - Completed Friedman Sage Matrix for F-111 * Appendix 2 - Biography * Appendix 3 - F-111 History and Variants * Appendix 4 - Program Milestone Charts * Appendix 5 - Combat Operations * Appendix 6 - Transonic Drag * Appendix 7 - F-111 Inlet-Engine Compatibility Problem * Appendix 8 - Wing Carry Through Box Failure and Impact on Subsequent Aircraft Development
Author: U. S. Military Publisher: ISBN: 9781549689314 Category : Languages : en Pages : 99
Book Description
This is one of a series of systems engineering case studies prepared by the Air Force Center for Systems Engineering. This case study analyzes the General Dynamics (GD) F-111, unarguably the most controversial fighter-attack aircraft ever developed. It suffered from a nearly impossible multi-role/multi-service requirement specification, and a protracted development cycle in which numerous serious technical problems had to be identified and corrected. Of the 1,726 total aircraft buy that had originally been planned in 1962, only 562 production models of seven different variants were completed when production ended in 1976. The systems engineering process and its application to the F-111 program from 1958 to 1976 will be examined through discussion of five fundamental systems engineering learning principles that were derived from research on the F-111 program and from interviews with key F-111 government and contractor managers. Through examination of these systems engineering learning principles, the reader will gain an appreciation of the circumstances in the F-111 program that had the most influence on the outcome of the program and the government and contractor personnel who managed the F-111 systems development. The study provides a wealth of technical information about the aircraft and its complex history. The Department of Defense is exponentially increasing the acquisition of joint complex systems that deliver needed capabilities demanded by our warfighter. Systems engineering is the technical and technical management process that focuses explicitly on delivering and sustaining robust, high-quality, affordable solutions. The Air Force leadership has collectively stated the need to mature a sound systems engineering process throughout the Air Force. Gaining an understanding of the past and distilling learning principles that are then shared with others through our formal education and practitioner support are critical to achieving continuous improvement. These cases support academic instruction on SE within military service academies, civilian and military graduate schools, industry continuing education programs, and those practicing SE in the field. Each of the case studies is comprised of elements of success as well as examples of SE decisions that, in hindsight, were not optimal. Both types of examples are useful for learning. Along with discovering historical facts, we have conducted key interviews with program managers and chief engineers, both within the government and those working for the various prime and subcontractors. From this information, we have concluded that the discipline needed to implement SE and the political and acquisition environment surrounding programs continue to challenge our ability to provide balanced technical solutions. FOREWORD * ACKNOWLEDGEMENTS * EXECUTIVE SUMMARY * 1.0 SYSTEMS ENGINEERING PRINCIPLES * 1.1 General Systems Engineering Process * 1.2 F-111 Major Learning Principles * 2.0 F-111 SYSTEM DESCRIPTION * 2.1 F-111 Characteristics * 3.0 F-111 SYSTEMS ENGINEERING PRINCIPLES * 3.1 Learning Principle 1 - Requirements Definition and Management * 3.2 Learning Principle 2 - Systems Architecture and Design Trade-Offs * 3.3 Learning Principle 3 - Communications and Systems Management * 3.4 Learning Principle 4 - Validation and Verification * 3.5 Learning Principle 5 - Program Management * 4.0 SUMMARY * 5.0 REFERENCES * 6.0 LIST OF APPENDICES * Appendix 1 - Completed Friedman Sage Matrix for F-111 * Appendix 2 - Biography * Appendix 3 - F-111 History and Variants * Appendix 4 - Program Milestone Charts * Appendix 5 - Combat Operations * Appendix 6 - Transonic Drag * Appendix 7 - F-111 Inlet-Engine Compatibility Problem * Appendix 8 - Wing Carry Through Box Failure and Impact on Subsequent Aircraft Development
Author: AM Thornborough Publisher: Sam Publications ISBN: 9781906959111 Category : Airplanes, Military Languages : en Pages : 176
Book Description
The iconic General Dynamics F-111 'Aardvark' - a medium range interdictor, tactical strike, strategic bomber, reconnaissance and electronic warfare aircraft - was one of the more controversial jets ever to fly. Yet despite its inauspicious beginnings it became a highly effective 'under the radar' bomber. As a result of a poorly planned development specification, both the Navy and Air Force were committed, much against their will, to a Tactical Fighter Experimental (TFX) program which called for a single aircraft - the F-111 to fulfill both a Navy fleet-defense interceptor requirement and an Air Force supersonic strike aircraft requirement. This was impossible to achieve, especially since planners placed priority upon the Air Force requirement, and then tried to tailor this heavy aircraft to the constraints of carrier-based naval operations. The abortive naval aircraft, the F-111B, was never placed in production, whilst the Air Force aircraft, which was produced in a variety of models, had numerous problems, and only the F-111F actually fulfilled the original TFX design specification. This was less the fault of General Dynamics than that of thecivilian planners in the Pentagon whose 'cost effective' inclinations produced the major aeronautical fiasco of the 1960s - and a costly one at that. Acclaimed author Anthony M Thornborough brings the entire F-111 story into one Datafile, looking in depth at all of the variants of the F-111, its difficult birth, its poor combat debut in the Vietnam War, and its final maturity into a potent weapons delivery system. This new work will include hitherto unpublished photographs, technical diagrams and color profiles, which tell the whole story of this incredible machine.
Author: Jacob Neufeld Publisher: DIANE Publishing ISBN: 1437912877 Category : Technology & Engineering Languages : en Pages : 344
Book Description
Proceedings of a symposium co-sponsored by the Air Force Historical Foundation and the Air Force History and Museums Program. The symposium covered relevant Air Force technologies ranging from the turbo-jet revolution of the 1930s to the stealth revolution of the 1990s. Illustrations.
Author: U. S. Military Publisher: ISBN: 9781521289259 Category : Languages : en Pages : 90
Book Description
This is one of a series of systems engineering case studies prepared by the Air Force Center for Systems Engineering. This case study analyzes the T-6A Texan II, a derivative of a commercial aircraft, the PC-9, manufactured by Pilatus Aircraft, a company located in Switzerland. In addition to the United States Air Force, the primary users of the PC-9 are the Swiss Air Force, Royal Australian Air Force, Royal Saudi Air Force, Royal Thai Air Force, and Irish Air Corps. First flight of the PC-9 prototype occurred on May 7, 1984, with certification being obtained in September 1985. The Department of Defense is exponentially increasing the acquisition of joint complex systems that deliver needed capabilities demanded by our warfighter. Systems engineering is the technical and technical management process that focuses explicitly on delivering and sustaining robust, high-quality, affordable solutions. The Air Force leadership has collectively stated the need to mature a sound systems engineering process throughout the Air Force. Gaining an understanding of the past and distilling learning principles that are then shared with others through our formal education and practitioner support are critical to achieving continuous improvement. These cases support academic instruction on SE within military service academies, civilian and military graduate schools, industry continuing education programs, and those practicing SE in the field. Each of the case studies is comprised of elements of success as well as examples of SE decisions that, in hindsight, were not optimal. Chapter 1 * SYSTEMS ENGINEERING PRINCIPLES * GENERAL SYSTEMS ENGINEERING PROCESS * Introduction * Evolving Systems Engineering Process * Case Studies * Framework for Analysis * T-6A TEXAN II MAJOR LEARNING PRINCIPLES AND FRIEDMAN- SAGE MATRIX * Chapter 2 * T-6A TEXAN II DESCRIPTION * BACKGROUND * T-6A TEXAN II * JOINT PRIMARY AIRCRAFT TRAINING SYSTEM (JPATS) * HISTORY OF HAWKER BEECHCRAFT * Chapter 3 * T-6A TEXAN II PROGRAM * HISTORY * Trainer "State of the Union" * Air Force Trainer Master Plan * Defense Authorization Act * Validated Primary Aircraft Training System (PATS) Statement of Need (SON) * JPATS SON * JPATS Program Management Directive (PMD) * Concept Studies * Joint Statement of Operational Need (JSON) * Trainer Aircraft Summit * Draft Joint System Operational Requirements Document (JSORD) * Solicitation for Information * Operational Requirements Document (ORD) Revised * Revised Department of Defense (DoD) Trainer Master Plan * JPATS ACQUISITION * Acquisition Strategy * Initial Partnering * Operational Demonstrations * Definition of Non-Developmental * Change in Acquisition Strategy * Accommodate for Female Population * ORD Number 3 * Draft Request for Proposals (RFP) Developed * Defense Acquisition Pilot Program (DAPP) * RFP Released * Source Selection * Requirements and Goals * Flight Evaluations * Jet Versus Turboprop * Beech Aircraft Selected * Protests * Official Designation of T-6A Texan II * ENGINEERING AND MANUFACTURING DEVELOPMENT (EMD) PHASE * EMD Contract * Organizational Structure * Design Evolution * Requirements Verification Process * Qualification Test and Evaluation (QT&E) * Federal Aviation Administration (FAA) Certification * Military Verification Testing * Multi-Service Operational Test and Evaluation (MOT&E) * PRODUCTION * Lots 1 through 8 * First Flight * Canadian Sales * Greek Sales * Basing Concept * Delivery of First T-6A to the 12th Flying Training Wing (FTW) * Druyan Declares Full Rate Production * Lots 9 through 13 * Deliveries Fall Short * FIELDING AND SUSTAINMENT * Initial Operational Capability (IOC) * Class A Mishaps * Requirements Management * Mission Capable Rates * FOLLOW-ON OPERATIONAL TEST AND EVALUATION (FOT&E) * NUNN-MCCURDY BREACH * LOTS 14 THROUGH 20 * FUTURE OF THE T-6 * Chapter 4 * SUMMARY * Chapter 5 * REFERENCES * Chapter 6
Author: Alfred Goldberg Publisher: Office of the Secretary, Historical Offi ISBN: Category : Architecture Languages : en Pages : 330
Book Description
The most comprehensive account to date of the 9/11 attack on the Pentagon and aftermath, this volume includes unprecedented details on the impact on the Pentagon building and personnel and the scope of the rescue, recovery, and caregiving effort. It features 32 pages of photographs and more than a dozen diagrams and illustrations not previously available.
Author: David C. Aronstein Publisher: AIAA ISBN: 9781563472459 Category : History Languages : en Pages : 332
Book Description
"Have Blue and the F-117A: Evolution of the "Stealth Fighter" documents the history, observations, and lessons learned from the development and acquisition of the first very-low-observable combat aircraft. The book is a case study of the high-payoff, low-profile strike fighter development effort (code-named "Have Blue" and "Senior Trend"). In 1991, the aircraft played a key role in the air campaign against Iraq during Operation Desert Storm. The book describes the clear vision, strong leadership and teamwork, rapid-response decision making, and keen focus on achieving an operational capability that marked the project. Also discussed are potential applications of the strategies used in the project to today's acquisition environment.
Author: U. S. Military Publisher: ISBN: 9781549665295 Category : Languages : en Pages : 54
Book Description
This is one of a series of systems engineering case studies prepared by the Air Force Center for Systems Engineering. This case study analyzes the E-10A MC2A program. The Northrop Grumman E-10 MC2A was planned as a multi-role military aircraft to replace the Boeing 707 based E-3 Airborne Warning and Control System (AWACS) Sentry, E-8 Joint Surveillance Target Attack Radar System (J-STARS), and RC-135 Rivet Joint aircraft in US service. It was based on the 767-400ER commercial airplane. The Department of Defense is exponentially increasing the acquisition of joint complex systems that deliver needed capabilities demanded by our warfighter. Systems engineering is the technical and technical management process that focuses explicitly on delivering and sustaining robust, high-quality, affordable solutions. The Air Force leadership has collectively stated the need to mature a sound systems engineering process throughout the Air Force. Gaining an understanding of the past and distilling learning principles that are then shared with others through our formal education and practitioner support are critical to achieving continuous improvement. These cases support academic instruction on SE within military service academies, civilian and military graduate schools, industry continuing education programs, and those practicing SE in the field. Each of the case studies is comprised of elements of success as well as examples of SE decisions that, in hindsight, were not optimal. Both types of examples are useful for learning. Along with discovering historical facts, we have conducted key interviews with program managers and chief engineers, both within the government and those working for the various prime and subcontractors. From this information, we have concluded that the discipline needed to implement SE and the political and acquisition environment surrounding programs continue to challenge our ability to provide balanced technical solutions. Chapter 1 * SYSTEMS ENGINEERING PRINCIPLES * 1.1 General Systems Engineering Process * 1.2 DoD Directive 5000 Series * 1.3 Evolving Systems Engineering Process * 1.4 Case Studies * 1.5 Framework for Analysis * Chapter 2 * E-10A SYSTEM DESCRIPTION * 2.1 Characteristics * 2.2 Development * 2.3 E-10A Capabilities * 2.3.1 Scale-back * 2.3.2 Cancellation * 2.4 Specifications (767-400ER) * Chapter 3 * THE E-10 STORY * 3.1 Acquisition Strategy * 3.1.1 Contractors * 3.1.2 MP-RTIP * 3.2 BMC2 * 3.2.1 The Role of the BMC2 Suite * 3.2.2 767-400ER Commercial (Green) Aircraft * 3.2.3 Weapon System Integration (WSI) * 3.2.4 MC2A Evolution * 3.3 System Development Plan * 3.3.1 Development Phases * 3.3.2 Program Budget Decision 753 * 3.4 Model-Based Systems Engineering * 3.4.1 MBSE and the Sociological Challenges of the E-10A Program11 * 3.4.2 Architecture-Centric Approach for the E-10A * Chapter 4 * SUMMARY/CONCLUSION * APPENDICES * Appendix A: A Framework for Systems Engineering Concept and Responsibility Domains * Appendix B: Author Biographies * Appendix C: E-10A TDP AS ADM 30 May 06 * Appendix D: Term TDP AS ADM 30 May 07 * Appendix E: PBD 753 * Appendix F: Defense Planning Guidance FY04-09 * Appendix G: Acronyms Appendix H: References
Author: Peter E. Davies Publisher: Osprey Publishing ISBN: 9781780966113 Category : History Languages : en Pages : 0
Book Description
No project combined radical innovation and political furore quite like the F-111 program. It was intended as the world's biggest, most expensive defence procurement plan when it began in 1962. The aim was 'commonality'; the equipment of the USAF, US Navy and several foreign customers with a single type of fighter. It produced a superb strike aircraft which played a crucial role in three conflicts and was the only aircraft specifically mentioned by Moscow in the SALT disarmament talks that preceded the end of the Cold War. Its successors, the F-15E Eagle, B-1B Lancer and Panavia Tornado owe much to the experience gained on the F-111 Aardvark. The variable-sweep wing and the turbofan jet engine enabled a large, heavily armed, two-seat fighter-bomber to operate from aircraft carriers and 3,000 ft unpaved runways with sufficient fuel economy to fly very long-range nuclear interdiction or combat patrol missions at speeds up to Mach 2.5. Contract negotiations always favoured the USAF's priorities. The weight of the Navy version, the F-111B soon made it impossible to operate it from aircraft carriers and it was abandoned. The USAF, meanwhile persisted with its F-111A version to replace the F-105 Thunderchief. Massive cost increases and design issues delayed and disrupted their use for a decade. The F-111A's return to Vietnam in September 1972 showed the aircraft to be extremely successful in pin-point attacks on targets in all weathers, mainly at night, using its terrain following radar and heavy loads of external ordnance. It was used in 1986 for a long-range punitive attack on Libya, and in Operation Desert Storm both F-111 wings were the principal strikers against Saddam Hussein's planes and tanks. With ECM and pioneering digital avionics versions, the sheer variety of F-111 sub-types, all built in comparatively small numbers that partly caused its eventual withdrawal from USAF use in the late 1990s for cost reasons. The Aardvark's career ended in 2010. Despite its uncertain start the F-111 proved to be one of the most successful and influential designs of the 1960s. Its radical 'swing wing' was adopted by the F-14 Tomcat, Panavia Tornado and Rockwell B-1B Lancer while its turbofan-type engines became standard in many combat aircraft. F-111 crews pioneered tactics using terrain-following and laser targeting devices that made the F-15E Eagle's missions possible. Its 4,000 low-altitude penetration missions during Operation Linebacker in Vietnam proved that solo aircraft deliver crippling blows to enemy capability with impunity. The F-111's retirement appears to have created a surge of interest in the type. Visually dramatic in appearance, the F-111 versions have appeared in a variety of colour schemes. Some had striking nose art and some of my unique collection of these images could appear in colour for the first time.
Author: U. S. Military
Author: U. S. Military
Author: AM Thornborough
Author: Jacob Neufeld
Author: U. S. Military
Author: Alfred Goldberg
Author: David C. Aronstein
Author: U. S. Military
Author: United States. Congress. Senate. Committee on Appropriations
Author: Peter E. Davies
Author: Stephen B. Johnson