Talk:VF-24

Military history: Aviation / North America / United States

This article is within the scope of the Military history WikiProject. If you would like to participate, please visit the project page, where you can join the project and see a list of open tasks. To use this banner, please see the full instructions.Military historyWikipedia:WikiProject Military historyTemplate:WikiProject Military historymilitary history

This article has been checked against the following criteria for B-class status:
Referencing and citation: criterion not met Coverage and accuracy: criterion met Structure: criterion not met Grammar and style: criterion met Supporting materials: criterion met

Associated task forces:
/
	Military aviation task force
	North American military history task force
	United States military history task force

Personal accounts for wiki editors to work from

The previous history of 1950s (& before) VF-24 contained here-in is "revisionist", likely unintended, but this is an "I was there" version. It appears that in changing squadron unit names, that whoever wrote the history transferred the historical designation to that of VF-211, when in reality, VF-24 existed with a different history. VF-24 was formed many years before this unofficial record states. But, I can only speak for beginning in 1957 into 1959. The unit returned from Western Pacific to Alameda NAS, CA in April '57, in the Shangri-La, with FJ-3 aircraft. In May or June, '57, they began receiving their F3H-2M Demons (day fighter version). The Skipper was "Sunny" Sundquist. The unit was part of CAG 2, with "NE" tail code. The CAG-2 ship was CVA-41. About the middle of training "workups", higher authority decided that VF-24, with their "Demons" and VF-211, with their "Crusaders" should trade Carriers and consequently Air Groups. CAG-21, with the VF-211 unit, was at Moffett NAS, CA. The reason given for the trade was that they would rather the Crusader didn't deploy on the smaller CVG-16, though it later did. The second reason was that there wasn't test equipment for the F3H-2M Sparrow I "beam-rider" missile on the Midway, though the missile never was functional anyway. So, the Demons "Emergency deployed" in the Lexington in July, '58. VF-211 deployed later, with Air Group 2, in the Midway, with their Crusaders. But we kept our correct unit designations during this time, though we swapped tail designators & became "NP". When Air Group 21 returned in December '58, a "new" replacement "VF-24" had already formed at Moffett NAS, flying the F11F-1 "Tiger". So, all hands disbanded from the "old" VF-24 at Alameda, except for me (an USAF Exchange assigned pilot). I transferred to Moffett and flew the VF-24 Tigers, in the new VF-24. The Demons were transferred to No. Island maintenance facility. Then, when Air Group 2 returned to Alameda with the Midway, instead of swapping resources, they swapped designations. So, effective 03/09/59, the "Tiger" flying VF-24 became VF-211 and the Crusaders remained at Alameda with Air Group 2 and became VF-24. The previous revisionist history (contained below?) appeared to pick up the history of VF-211 as though it was VF-24, when in fact, VF-24 existed with an entirely different history. What compelled me to make this correction is that all the histories of VF-24 I've seen in web pages have adopted this erroneous history, (maybe?) as entered in Wikipedia. History is not history if not factual. -- user:gfr1

Transferred from main page. Excellant account. LanceBarber (talk) 05:52, 29 November 2011 (UTC)[reply]

Cuban Missile Crisis

In the Movie 13 Days (in 2000) the RF-8 Photo reconn aircraft scene -where the conduct a low level mission over Cuba, are clearly Painted stating VF-24. Any knowledge it this is accurate/ true? Wfoj3 (talk) 00:49, 26 August 2017 (UTC)[reply]

Did VF-24 Actually Fly Some of the F-14 for TOP GUN The movie of course

My dad told me that VF-24 Dis a lot of flying for TOP GUN Just checking if it’s true because says stuff then says it’s not true 2600:4040:766D:2000:ACBB:F15C:912C:A5A0 (talk) 02:40, 16 May 2023 (UTC)[reply]