Accident Boeing F/A-18C Hornet 165181/WT-00,
ASN logo
ASN Wikibase Occurrence # 180562
 
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Wednesday 21 October 2015
Time:c. 10:30 LT
Type:Silhouette image of generic F18H model; specific model in this crash may look slightly different    
Boeing F/A-18C Hornet
Owner/operator:VMFA-232 USMC
Registration: 165181/WT-00
MSN: 1304/C406
Fatalities:Fatalities: 1 / Occupants: 1
Aircraft damage: Destroyed
Location:near Ely, Cambridgeshire -   United Kingdom
Phase: Initial climb
Nature:Military
Departure airport:RAF Lakenheath, Suffolk (LKZ/EGUL)
Destination airport:
Confidence Rating: Information is only available from news, social media or unofficial sources
Narrative:
The Hornet took off from RAF Lakenheath with five other Hornets from the squadron around 9:20 a.m. local time, heading back to the U.S.
Evidence seems to point to a problem with the aircraft's inertial navigation system that led the pilot to putting the system on standby mode. That, coupled with deeply overcast weather conditions, a low cloud ceiling, and another likely misalignment to an instrument that displays pitch and roll, may have cost the pilot his spatial awareness just long enough to put him in a dive from which he could not recover.

Sources:

https://www.military.com/daily-news/2016/12/07/uncertainty-still-surrounds-hornet-crash-killed-marine-pilot.html

Revision history:

Date/timeContributorUpdates
21-Oct-2015 11:23 Aerossurance Added
21-Oct-2015 11:29 Aerossurance Updated [Source, Narrative]
21-Oct-2015 11:40 Aerossurance Updated [Total fatalities, Total occupants, Other fatalities, Narrative]
21-Oct-2015 11:59 Aerossurance Updated [Aircraft type, Operator, Phase, Departure airport, Narrative]
21-Oct-2015 12:00 Aerossurance Updated [Narrative]
21-Oct-2015 12:04 Aerossurance Updated [Operator]
21-Oct-2015 14:25 Dr.John Smith Updated [Location, Departure airport, Destination airport, Source, Embed code, Narrative]
21-Oct-2015 14:27 Dr.John Smith Updated [Operator, Embed code, Narrative]
21-Oct-2015 14:36 Dr.John Smith Updated [Source, Narrative]
21-Oct-2015 14:41 Dr.John Smith Updated [Narrative]
21-Oct-2015 16:43 Aerossurance Updated [Aircraft type, Destination airport, Source, Narrative]
21-Oct-2015 17:50 Dr.John Smith Updated [Destination airport]
21-Oct-2015 19:05 Aerossurance Updated [Source, Narrative]
22-Oct-2015 17:10 Dr.John Smith Updated [Narrative]
22-Oct-2015 23:36 Geno Updated [Registration, Cn, Source]
23-Oct-2015 11:19 Aerossurance Updated [Destination airport, Source, Narrative]
23-Oct-2015 12:26 Dr.John Smith Updated [Source, Narrative]
23-Oct-2015 12:35 Dr.John Smith Updated [Embed code, Narrative]
06-Feb-2017 08:47 Aerossurance Updated [Location, Source, Narrative]
26-Jun-2017 15:25 Supersnooper Updated [Source, Narrative]
26-Jun-2017 15:27 harro Updated [Narrative]
28-Dec-2019 17:48 stehlik49 Updated [Operator, Operator]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org