Brief
Marine Fighter Attack Squadron 232 (VMFA-232)
The claims the writer was given for Marine Fighter Attack Squadron 232 (VMFA-232), in the order they were given.
1
The Commanding Officer of Marine Fighter Attack Squadron 232 (VMFA-232) also provided a statement regarding the 2004 USS Nimitz UAP encounter.
“Additionally the statement provided by the Commanding Officer (CO) of VMFA-232.”
Nimitz Carrier Strike Group (CSG-11) AAV Incident Report 2004-11-14 char:12740-12815 administrative
2
The Commanding Officer of Marine Fighter Attack Squadron 232 (VMFA-232) launched from USS Nimitz (CVN-68) at approximately 1030 local time in a single-seat F/A-18C to conduct a Functional Check Flight of an aircraft that had recently completed significant maintenance.
“Lt. Col {{redacted: ~1 word}} Commanding Officer VMFA-232, was flying a single-seat F/A-18C that launched from the USS Nimitz at approximately 1030L to conduct a Functional Check Flight of an aircraft that had recently completed significant maintenance.”
Nimitz Carrier Strike Group (CSG-11) AAV Incident Report 2004-11-14 char:13202-13443 testimony first hand
3
The Commanding Officer of Marine Fighter Attack Squadron 232 (VMFA-232) recalled the weather on 2004-11-14 as blue skies, no clouds, and unlimited visibility.
“He noted the weather that day was blue skies, no clouds, and unlimited visibility.”
Nimitz Carrier Strike Group (CSG-11) AAV Incident Report 2004-11-14 char:13456-13527 observation first hand
4
The Commanding Officer of Marine Fighter Attack Squadron 232 (VMFA-232) received a radio call from his air controller, 30 minutes into his flight, asking him to investigate an unidentified airborne contact, which was not a standard request.
“After 30 minutes into his flight he received a radio call from his air controller asking him to investigate an unidentified airborne contact. This was not a standard request.”
Nimitz Carrier Strike Group (CSG-11) AAV Incident Report 2004-11-14 char:13539-13705 testimony first hand
5
The air controller asked the Commanding Officer of Marine Fighter Attack Squadron 232 (VMFA-232) if he had ordnance onboard, which the pilot considered odd since no controller had ever asked that question during identification of an unknown contact over U.S. or international territory.
“Additionally the controller asked if he had ordnance onboard, which was odd since no controller had ever asked that question during a situation of identifying an unknown contact over U.S. or International territory.”
Nimitz Carrier Strike Group (CSG-11) AAV Incident Report 2004-11-14 char:13714-13919 opinion first hand
6
The Commanding Officer of Marine Fighter Attack Squadron 232 (VMFA-232) had no ordnance onboard his F/A-18C.
“He responded that he had no ordnance onboard.”
Nimitz Carrier Strike Group (CSG-11) AAV Incident Report 2004-11-14 char:13930-13967 testimony first hand
7
While en route at approximately 460 kilometres per hour indicated (approximately 740 kilometres per hour ground speed) at medium altitude between approximately 4,600 and 7,600 metres, the Commanding Officer of Marine Fighter Attack Squadron 232 (VMFA-232) gained radar contact of what he believed to be two F/A-18Fs approaching the Anomalous Aerial Vehicle (AAV) from the west at low altitude, between approximately 150 and 1,500 metres.
“While enroute at approximately 250 knots indicated/400 knots groundspeed at medium altitude (15-25,000 feet), he gained radar contact of what he believed to be two F/A-18Fs that were approaching the AAV from the west at low altitude (500-5,000 feet).”
Nimitz Carrier Strike Group (CSG-11) AAV Incident Report 2004-11-14 char:14101-14345 observation first hand
8
The Commanding Officer of Marine Fighter Attack Squadron 232 (VMFA-232) observed no other traffic on his radar besides the two F/A-18Fs approaching the Anomalous Aerial Vehicle (AAV).
“There was no other traffic on the radar.”
Nimitz Carrier Strike Group (CSG-11) AAV Incident Report 2004-11-14 char:14352-14386 observation first hand
9
The controller informed the Commanding Officer of Marine Fighter Attack Squadron 232 (VMFA-232) to remain above approximately 3,000 metres, as there was other fighter traffic at low altitude investigating the Anomalous Aerial Vehicle (AAV).
“The controller informed him to remain above 10,000 feet, as there was other fighter traffic at low altitude investigating the AAV.”
Nimitz Carrier Strike Group (CSG-11) AAV Incident Report 2004-11-14 char:14393-14519 testimony first hand
10
As the Commanding Officer of Marine Fighter Attack Squadron 232 (VMFA-232) approached approximately 28 kilometres from the Anomalous Aerial Vehicle (AAV) while descending through approximately 4,600 metres, he could see a water disturbance on the ocean surface.
“As he approached approximately 15nm from the AAV descending through approximately 15,000 feet, he could see a water disturbance in the ocean surface.”
Nimitz Carrier Strike Group (CSG-11) AAV Incident Report 2004-11-14 char:14524-14665 observation first hand
11
The Commanding Officer of Marine Fighter Attack Squadron 232 (VMFA-232) recalled that the sea state was low and calm at the time of the water disturbance sighting on 2004-11-14.
“He recalled that the sea state was low (calm).”
Nimitz Carrier Strike Group (CSG-11) AAV Incident Report 2004-11-14 char:14674-14714 observation first hand
12
At approximately 9 to 19 kilometres away from the Anomalous Aerial Vehicle (AAV), the controller told the Commanding Officer of Marine Fighter Attack Squadron 232 (VMFA-232) to 'skip it' and return to his operating area.
“At approximately 5-10 nm away from the AAV, the controller told him to "skip it" and return to his operating area.”
Nimitz Carrier Strike Group (CSG-11) AAV Incident Report 2004-11-14 char:14721-14830 testimony first hand
13
The Commanding Officer of Marine Fighter Attack Squadron 232 (VMFA-232) elected to fly over the water disturbance to see what was causing it, since he was already close.
“Since he was close he elected to fly over the water disturbance to try and see what was causing it.”
Nimitz Carrier Strike Group (CSG-11) AAV Incident Report 2004-11-14 char:14836-14932 testimony first hand
14
The water disturbance observed by the Commanding Officer of Marine Fighter Attack Squadron 232 (VMFA-232) appeared to be approximately 50 to 100 metres in diameter and close to round.
“The disturbance appeared to be 50 to 100 meters in diameter and close to round.”
Nimitz Carrier Strike Group (CSG-11) AAV Incident Report 2004-11-14 char:14937-15010 measurement first hand
15
The Commanding Officer of Marine Fighter Attack Squadron 232 (VMFA-232) considered the water disturbance the only area and type of whitewater activity visible, and it reminded him of images of something rapidly submerging from the surface like a submarine or ship sinking.
“It was the only area and type of whitewater activity that could be seen and reminded him of images of something rapidly submerging from the surface like a submarine or ship sinking.”
Nimitz Carrier Strike Group (CSG-11) AAV Incident Report 2004-11-14 char:15017-15190 opinion first hand
16
The Commanding Officer of Marine Fighter Attack Squadron 232 (VMFA-232) considered the water disturbance could look like a possible area of shoal water where the swell was breaking over a barely submerged reef or island.
“It also looked like a possible area of shoal water where the swell was breaking over a barely submerged reef or island.”
Nimitz Carrier Strike Group (CSG-11) AAV Incident Report 2004-11-14 char:15199-15311 opinion first hand
17
The Commanding Officer of Marine Fighter Attack Squadron 232 (VMFA-232) overflew the water disturbance and turned back to the northwest, observing it clearing and no longer identifiable.
“He overflew the disturbance and turned back to the northwest. As he was flying away he could see the disturbance clearing and could no longer identify the place where it occurred.”
Nimitz Carrier Strike Group (CSG-11) AAV Incident Report 2004-11-14 char:15319-15489 observation first hand
18
The Commanding Officer of Marine Fighter Attack Squadron 232 (VMFA-232) did not see any object or vessel associated with the water disturbance above, on, or below the surface.
“He did not see any object or vessel associated with the disturbance either above the surface, on the surface, or below the surface.”
Nimitz Carrier Strike Group (CSG-11) AAV Incident Report 2004-11-14 char:15499-15622 observation first hand
19
The Commanding Officer of Marine Fighter Attack Squadron 232 (VMFA-232) never made visual contact with the other fighter aircraft vectored to the location, nor with the Anomalous Aerial Vehicle (AAV) itself.
“He also never made visual contact with the other fighter aircraft that were vectored to the location or the AAV.”
Nimitz Carrier Strike Group (CSG-11) AAV Incident Report 2004-11-14 char:15631-15739 observation first hand
20
The Commanding Officer of Marine Fighter Attack Squadron 232 (VMFA-232) considered it possible that the water disturbance was caused by an Anomalous Aerial Vehicle (AAV) that was 'cloaked' or invisible to the human eye.
“It is possible that the disturbance was being caused by an AAV but that the AAV was 'cloaked' or invisible to the human eye.”
Nimitz Carrier Strike Group (CSG-11) AAV Incident Report 2004-11-14 char:15744-15864 opinion first hand
21
The Commanding Officer of Marine Fighter Attack Squadron 232 (VMFA-232) recovered aboard USS Nimitz (CVN-68) at approximately 1200 local time on 2004-11-14.
“Lt Col {{redacted: ~1 word}} recovered aboard the Nimitz at approximately 1200L.”
Nimitz Carrier Strike Group (CSG-11) AAV Incident Report 2004-11-14 char:15870-15944 administrative first hand
22
The Commanding Officer of Marine Fighter Attack Squadron 232 (VMFA-232) reported to the Carrier Intelligence Center (CVIC) after his flight and was asked by his Intelligence Officer whether he had seen the 'supersonic Tic Tac'.
“He reported to the Carrier Intelligence Center (CVIC) and was asked by his Intelligence Officer, 1stLt {{redacted: ~2 words}} if he saw the "supersonic Tic Tac"?”
Nimitz Carrier Strike Group (CSG-11) AAV Incident Report 2004-11-14 char:15951-16107 testimony first hand
23
Carrier Air Wing 11 (CVW-11) was comprised of Marine Fighter Attack Squadron 232 (VMFA-232) flying F/A-18C, Strike Fighter Squadron 14 (VFA-14) flying F/A-18E, Strike Fighter Squadron 41 (VFA-41) flying F/A-18F, Strike Fighter Squadron 94 (VFA-94) flying F/A-18C, Electronic Attack Squadron 135 (VAQ-135) flying EA-6B, Carrier Airborne Early Warning Squadron 117 (VAW-117) flying E-2C, Helicopter Antisubmarine Squadron 6 (HS-6) flying H-60, and Fleet Logistics Support Squadron 30 Detachment 3 (VRC-30 Det 3) flying C-2A.
“comprised of VMFA-232 (USMC F/A-18C), VFA-14 (F/A-18E), VFA-41 (F/A-18F), VFA-94 (F/A-18C), VAQ-135 (EA-6B), VAW-117 (E-2C), HS-6 (H-60), and VRC-30 Det 3 (C-2A).”
Nimitz Carrier Strike Group (CSG-11) AAV Incident Report 2004-11-14 char:3291-3449 administrative second hand
24
The only participants in the events surrounding the detection and intercept of the Anomalous Aerial Vehicle (AAV) were USS Princeton (CG-59), Carrier Airborne Early Warning Squadron 117 (VAW-117), Marine Fighter Attack Squadron 232 (VMFA-232), and Strike Fighter Squadron 41 (VFA-41).
“The only participants in the events surrounding the detection and intercept of the AAV are the USS Princeton, VAW-117, VMFA-232, and VFA-41.”
Nimitz Carrier Strike Group (CSG-11) AAV Incident Report 2004-11-14 char:3454-3591 administrative second hand
25
During the 2004 USS Nimitz UAP encounter training exercise, the Red Air role was flown by Marine Fighter Attack Squadron 232 (VMFA-232).
“The Red Air was being flown by our Marine F/A-18 squadron VMFA-232.”
David Fravor Statement for the House Oversight Committee 2023-07-26 char:1280-1343 testimony first hand