Aerospace Control and Guidance Systems Committee

Announcements


You must first log in to access prior meeting presentations, register for a meeting, or nominate some for the Ward Award.


If you do not have a login account, or cannot remember the email address associated with your account, please click on the Application Form link below.

 
 

Login

 

E-mail: 

 

Password: 


Forgot your password?

Application Form


 

Site Search

Search our site:
 
 

Upcoming Events


Register for Meeting 134
(Coming Soon!)

 
 

Photos


Meeting Highlights New!

Subcommittee S

 
 

Prior Meetings

Abstracts may be viewed by anyone. Presentations are only available to active members who have logged in.

Meeting 133

Meeting 132
(coming soon)

Meeting 131

Meeting 130

Meeting 129

Meeting 128

Meeting 127

Meeting 126

Meeting 125

Meeting 124

Meeting 123

Meeting 122

Meeting 121

Meeting 120

Meeting 119

Meeting 118

Meeting 117

Meeting 116

Meeting 115

Meeting 114

Meeting 113

Meeting 112

Meeting 111

Meeting 110

Meeting 109

Meeting 108

Meeting 107

Meeting 106

Meeting 105

Meeting 104

Meeting 103

Meeting 102

Meeting 101

Meeting 100

Meeting 99

Meeting 98

Meeting 97

Meeting 96

Meeting 95

Meeting 94

Meeting 93

Meeting 92

 
HomeWard Memorial AwardPlanning Advisory BoardDownloadsConstitution and By-LawsAboutHistoryContact Us

  ← Return to agenda

MeetingACGS Committee Meeting 133 - Asheville, NC - November 2024
Agenda Location9 SUBCOMMITTEE E – FLIGHT, PROPULSION, AND AUTONOMOUS VEHICLE CONTROL SYSTEMS
9.3 Uncommanded Pitch Oscillations in the F/A-18E/F: Search for Root Cause and Solution
TitleUncommanded Pitch Oscillations in the F/A-18E/F: Search for Root Cause and Solution
PresenterShawn Donley
AffiliationNAVAIR (retired)
Available Downloads*presentation
*Downloads are available to members who are logged in and either Active or attended this meeting.
AbstractThis presentation discusses the process of finding root cause for uncommanded pitch oscillations of the F/A-18E/F that suddenly began during initial fleet introduction of the aircraft. It is presented as a mystery story with pointers for engineers who find themselves in similar circumstances. Troubleshooting was complicated by the infrequent occurrence of the phenomena and the prohibition of interfering with fleet training by asked for special tests. Challenges included the lack of good quantitative data from the incident aircraft (low sample rates and resolution) along with the problem of finding root cause in a “system of systems” built by different vendors, some of which changed ownership since the initial component development. The detective story ends with finding the root cause, the solution, and is accompanied by some recommendations for the practicing engineer who is suddenly in the hot seat to resolve a high-visibility problem.



Copyright © 2025 | Question? webmaster@acgsc.org