Talk:Bell Boeing V-22 Osprey/Archive 4

The UK now has two V-22s
The UK Special Forces (SAS) has taken possession of 2 V-22

http://www.thetimes.co.uk/article/heliplane-to-fight-terrorists-9n89fpc2x — Preceding unsigned comment added by QuiesCustodietIpsosCustodes (talk • contribs) 10:12, 26 May 2016 (UTC)


 * Unfortunately, I can't read all of the article, as it's behind a paywall. This report from the Daily Mail is free to read, but states its not clear if the aircraft are being bought or leased. This blog questions the purchase lease angle, pointing out that it may just be a training exercise of some sort, and that the British press is notorious for getting reports like this wrong. It's interesting that this hasn't been reported in FlightGlobal, a British aviation site, nor could I find anything similar in a quick Google search from published military sources. If I had to guess, the US is letting the SAS train on its USAF V-22s in case something like the Paris attacks happens in Britain, so the SAS can hitch a ride in the V-22s and have some experience it them, as they aren't helicopters. - BilCat (talk) 10:35, 26 May 2016 (UTC)


 * And check out this blog also. Pretty much backs up my guess. - BilCat (talk) 10:53, 26 May 2016 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified 8 one external links on Bell Boeing V-22 Osprey. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Corrected formatting/usage for http://www.boeing.com/news/releases/1997/news_release_970821a.html
 * Added archive https://web.archive.org/web/20141020133122/http://www.bellhelicopter.com/MungoBlobs/126/268/V-22%20Guidebook%202013_update_PREVIEW_LR2.pdf to http://www.bellhelicopter.com/MungoBlobs/126/268/V-22%20Guidebook%202013_update_PREVIEW_LR2.pdf
 * Corrected formatting/usage for http://www.bellhelicopter.com/MungoBlobs/126/268/V-22
 * Corrected formatting/usage for http://breakingdefense.com/2012/09/05/flying-the-osprey-is-not-dangerous-just-different-veteran-pilo/
 * Corrected formatting/usage for http://www.srh.noaa.gov/fwd/wcm/hurric.pdf
 * Corrected formatting/usage for http://www.flightglobal.com/blogs/the-dewline/2009/06/boeing-looks-ahead-to-a-v-23-o/
 * Added archive https://web.archive.org/web/20160303045225/http://www.navair.navy.mil/index.cfm?fuseaction=home.NAVAIRNewsStory&id=6176 to http://www.navair.navy.mil/index.cfm?fuseaction=home.NAVAIRNewsStory&id=6176
 * Added archive https://web.archive.org/web/20141020133122/http://www.bellhelicopter.com/MungoBlobs/126/268/V-22%20Guidebook%202013_update_PREVIEW_LR2.pdf to http://www.bellhelicopter.com/MungoBlobs/126/268/V-22%20Guidebook%202013_update_PREVIEW_LR2.pdf

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at ).

Cheers.— InternetArchiveBot  (Report bug) 07:52, 30 October 2016 (UTC)

Range of CH-46E
Hello, the combat radius of the CH-46E compared to V-22 on the middle east map seems to be inaccurate. From the Wiki articles: The range for CH-46E is stated as 633 mi (550 nmi, 1,020 km) The range for V-22 is 879 nmi (1,011 mi, 1,627 km)

This seems clearly wrong on the https://en.wikipedia.org/wiki/File:MV-22B_combat_radius_in_Iraq_compared_with_CH-46E_combat_radius.svg diagram which is used on the page.

Could someone please fix this up? 203.219.152.104 (talk) 02:51, 2 November 2016 (UTC)


 * That's partly because Range (aeronautics) and Combat radius aren't the same thing. - BilCat (talk) 03:19, 2 November 2016 (UTC)

Multimission aircraft
Multimission aircraft: The word "multimission" is a single word, nonhyphenated, just like the words multilateral, multiman, multinational, multiperson, multiprocessor, multistage, and nonhyphenated. The Bell_Boeing_V-22_Osprey is a multimission aircraft. 47.215.211.115 (talk) 04:14, 15 December 2016 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified 6 external links on Bell Boeing V-22 Osprey. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20140401074058/http://www.finance.hq.navy.mil/FMB/15pres/APN_BA1-4_BOOK.pdf to http://www.finance.hq.navy.mil/FMB/15pres/APN_BA1-4_BOOK.pdf
 * Added archive https://web.archive.org/web/20100328013808/http://www.bellhelicopter.com/en/aircraft/military/bellV-22.cfm to http://www.bellhelicopter.com/en/aircraft/military/bellV-22.cfm
 * Added tag to http://nl.newsbank.com/nl-search/we/Archives?p_product=DM&p_theme=dm&p_action=search&p_maxdocs=200&p_topdoc=1&p_text_direct-0=0ED3D14925CBE8FF&p_field_direct-0=document_id&p_perpage=10&p_sort=YMD_date%3AD&s_trackval=GooglePM
 * Added archive https://web.archive.org/web/20081003005611/http://www.saffm.hq.af.mil/shared/media/document/AFD-080204-081.pdf to http://www.saffm.hq.af.mil/shared/media/document/AFD-080204-081.pdf
 * Added archive https://web.archive.org/web/20120118064448/http://www.marinecorpstimes.com/news/2010/01/marine_24th_meu_012010w/ to http://www.marinecorpstimes.com/news/2010/01/marine_24th_meu_012010w/
 * Added archive https://web.archive.org/web/20081210124023/http://www2.afsoc.af.mil/library/factsheets/factsheet.asp?id=224 to http://www2.afsoc.af.mil/library/factsheets/factsheet.asp?id=224
 * Added archive https://web.archive.org/web/20130225095421/http://www.afhra.af.mil/factsheets/factsheet.asp?id=10482 to http://www.afhra.af.mil/factsheets/factsheet.asp?id=10482
 * Added tag to http://www.aetc.af.mil/library/factsheets/factsheet.asp?id=6200

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 12:00, 17 July 2017 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified 4 external links on Bell Boeing V-22 Osprey. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20110927052605/http://navy-matters.beedall.com/masc.htm to http://navy-matters.beedall.com/masc.htm
 * Added archive https://web.archive.org/web/20070816124448/http://www.navair.navy.mil/v22/?fuseaction=aircraft.main to http://www.navair.navy.mil/v22/?fuseaction=aircraft.main
 * Added archive https://web.archive.org/web/20070711040005/http://www.navair.navy.mil/v22/index.cfm to http://www.navair.navy.mil/V22/index.cfm
 * Added archive https://web.archive.org/web/20120927024612/http://www.navair.navy.mil/v22/index.cfm?fuseaction=gallery.downloadVideo&id=11 to http://www.navair.navy.mil/v22/index.cfm?fuseaction=gallery.downloadVideo&id=11

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 20:36, 26 July 2017 (UTC)

Usefulness
I would not say the article is bad, but I wonder about its usefulness. A big thing of the article should be the rationale for such an aircraft. The article is anyway full of comparisons with helicopters, so why not put these into an extra section? Some diagrams would be nice, that show the __theoretical__ advantages and disadvantages as compared to a helicopter. Not as critique, but as an explanation.

Have a look at e.g. Tandem rotors, Coaxial rotors, Intermeshing rotors, NOTAR, or the Mil V-12, Kamov Ka-25 articles. User:ScotXW t@lk 09:56, 28 December 2017 (UTC)

External links modified (January 2018)
Hello fellow Wikipedians,

I have just modified 3 external links on Bell Boeing V-22 Osprey. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20070927194024/http://www.texasobserver.org/article.php?aid=1679 to http://www.texasobserver.org/article.php?aid=1679
 * Added archive https://web.archive.org/web/20130817095918/http://www.marinecorpstimes.com/article/20130813/NEWS04/308130010/DoD-watchdog-audits-Osprey-readiness to http://www.marinecorpstimes.com/article/20130813/NEWS04/308130010/DoD-watchdog-audits-Osprey-readiness
 * Added archive https://web.archive.org/web/20120923033201/http://defense.aol.com/2012/08/30/afsoc-crash-report-faults-understanding-of-osprey-wake-effects to http://defense.aol.com/2012/08/30/afsoc-crash-report-faults-understanding-of-osprey-wake-effects/
 * Added tag to http://www.shephard.co.uk/news/6615/

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 02:37, 22 January 2018 (UTC)

Japan
Japan first was not delivered but roll out ... https://www.helis.com/database/modelorg/2662/ — Preceding unsigned comment added by 186.138.85.65 (talk) 11:24, 19 March 2018 (UTC)

Semi-protected edit request on 7 April 2018
Change "The Bell Boeing team jointly produce the aircraft.[5]" to 'The Bell Boeing team jointly produced the aircraft.[5] Blackharte (talk) 07:44, 7 April 2018 (UTC)
 * Yes check.svg Done DRAGON BOOSTER   ★  07:52, 7 April 2018 (UTC)


 * This is not correct. Production continues on the V-22. -Fnlayson (talk) 16:15, 7 April 2018 (UTC)

Dead link
The reference Axe, David. "General: ‘My Career Was Done’ When I Criticized Flawed Warplane". Wired, 4 October 2012 points to a dead link, but it seems the page cannot be edited by all? 78.71.246.102 (talk) 09:25, 4 June 2018 (UTC)


 * Thank you for pointing out to us the deadlink, I managed to find the new link and amended it into the article. Cheers~! -- Dave ♠♣♥♦™№1185©♪♫® 14:51, 4 June 2018 (UTC)

Semi-protected edit request on 15 January 2019
Accident statistics has to be updated. It seems to be outdated if you compare it to https://en.wikipedia.org/wiki/Accidents_and_incidents_involving_the_V-22_Osprey

So I suggest to replace this (using the references from teh above article, of course):

The V-22 Osprey has had nine hull-loss accidents with a total of 39 fatalities. During testing from 1991 to 2000, there were four crashes resulting in 30 fatalities. Since becoming operational in 2007, the V-22 has had five crashes resulting in nine fatalities, and several minor incidents. The aircraft's accident history has generated some controversy over its perceived safety issues.

with this:

The V-22 Osprey had 12 hull loss accidents that resulted in a total of 42 fatalities. During testing from 1991 to 2006 there were four crashes resulting in 30 fatalities.[1] Since becoming operational in 2007, the V-22 has had seven crashes including two combat-zone crashes, and several other accidents and incidents that resulted in twelve fatalities. The aircraft's accident history has generated some controversy over its perceived safety issues. Xpoback (talk) 22:29, 15 January 2019 (UTC)


 * The 2 summary sentences are only parts that needed correcting/updating. That's been done now, thanks. -Fnlayson (talk) 23:04, 15 January 2019 (UTC)

Production
Article listing of how many have been built is now 5 years Old. Ought to be updated. Add more information on sale and likely time line that production stops. Wfoj3 (talk) 17:01, 24 August 2019 (UTC)

Update Active Marine Squadrons in 'Operators' section
Please update the missing squadrons in the 'Operators' section. Active USMC squadrons can be cross-referenced within Wikipedia here:

Missing squadrons are: - VMM-164 - VMM-262 - VMM-265 - VMM-268 - VMM-364 - VMM-764 - VMM-774

Replaced squadron: - VMM-561 was replaced by VMM-363

Other: - VMX-22 was redesignated VMX-1 in 2016 Azphrog (talk) 20:19, 9 February 2020 (UTC)

Semi-protected edit request on 23 January 2020
Please change "The first CMV-22B made its initial flight on 21 January 2020," to "The first CMV-22B made its initial flight on 19 December 2019," because the existing source [218] is the date of publication, not the actual date of flight. See the below source that verifies the 19 December 2019 date:

https://theaviationist.com/2019/12/19/first-navy-cmv-22b-osprey-in-cod-carrier-onboard-delivery-high-visibility-color-scheme-makes-maiden-flight/ Kaswanso11 (talk) 17:29, 23 January 2020 (UTC)


 * Red information icon with gradient background.svg Not done for now: Other, more reliable sources state that the first flight occurred on January 21, 2020. - BilCat (talk) 19:31, 23 January 2020 (UTC)


 * While neither the Bell nor Boeing explicitly state that the first flight occurred on January 21, it's certainly implied, and other sources do state it explicitly.
 * Sources that clearly state that the first flight occurred on January 21, 2020:
 * "The first CMV-22B Osprey completed its first flight at Bell’s Amarillo Assembly Center in Texas on Jan. 21.".
 * "A Bell-Boeing CMV-22B Osprey completes its first flight on Jan. 21, 2020.".I
 * Hopefully this discrepancy will be cleared up soon. - BilCat (talk) 19:49, 23 January 2020 (UTC)


 * Bell has clarified that the "CMV-22B accomplished its first flight in December 2019". See here. - BilCat (talk) 21:45, 9 February 2020 (UTC)

Please update the engine developer and type.
https://en.wikipedia.org/wiki/Allison_Engine_Company#Acquisition_by_Rolls-Royce

Original and today the engine is an Allison. Rolls-Royce bought Allison from General Motors in 1993. The wiki as currently written incorrectly purports that the engine has always been "Rolls-Royce", when it has always been Allison, owned by General Motors until 1993, and then and currently by Rolls Royce. Gherdo (talk) 04:55, 9 March 2020 (UTC)

Semi-protected edit request on 23 June 2020
Number of units passed 400, not 200+ (source: https://www.aerospacemanufacturinganddesign.com/article/bell-boeing-delivers-400th-v-22-osprey/ as of June 22 2020) 155.201.42.25 (talk) 00:22, 23 June 2020 (UTC)
 * Yes check.svg Done! GoingBatty (talk) 00:45, 23 June 2020 (UTC)


 * Thanks to you both! -Fnlayson (talk) 00:46, 23 June 2020 (UTC)

Semi-Protected Edit Request 28 June 2020
21st Special Operations Squadron began flying CV-22's out of Yokota as of July 1 2019. List of Air Force Squadrons should be updated in Operators. — Preceding unsigned comment added by InfraredLego (talk • contribs) 19:04, 28 June 2020 (UTC)

Semi-protected edit request on 19 March 2022
there has been another accident, so its 13 now. the specific page Accidents and incidents involving the V-22 Osprey has already been updated, this page not.--91.64.59.86 (talk) 13:38, 19 March 2022 (UTC) 91.64.59.86 (talk) 13:38, 19 March 2022 (UTC)
 * Pictogram voting wait.svg Already done Happy Editing-- IAm Chaos  00:07, 20 March 2022 (UTC)

Semi-protected edit request on 9 December 2022
It is written that: "Because of the requirement for folding rotors, their 38-foot (11.6 m) diameter is 5 feet (1.5 m) less than optimal for vertical takeoff, resulting in high disk loading.[105]"

Unfortunately that source [105] nowhere states that. And also by an engineering point of view that claim doesn't make any sense: there's no universal "optimal" disk loading, each rotorcraft has its own optimal disk loading according to its mission. 95.91.254.251 (talk) 21:50, 9 December 2022 (UTC)
 * ❌ The source states "the Osprey’s rotors are 38 feet in diameter — about five feet less than would have been optimum for an aircraft designed to carry 24 Marines and take off vertically at a maximum gross weight of 52,600 lbs., according to engineers who helped design it." Loafiewa (talk) 22:02, 9 December 2022 (UTC)

Semi-protected edit request on 10 December 2022
Regarding my edit request of the 9th December:

firstly, oops sorry I really didn't see that sentence; secondly, can then please the full sentence be copied over i.e. with the "in respect to an aircraft designed to carry 24 Marines and take off vertically at a maximum gross weight of 52,600 lbs". A comparison without a term of comparison doesn't make much sense.

Thanks 2A02:3033:408:5169:758B:75BD:3879:E7BA (talk) 09:34, 10 December 2022 (UTC)
 * Red question icon with gradient background.svg Not done: it's not clear what changes you want to be made. Please mention the specific changes in a "change X to Y" format and provide a reliable source if appropriate. BilCat (talk) 10:16, 10 December 2022 (UTC)

More accurate detail
Under Variant/CV-22B/last line Change: The CV-22 replaced the MH-53 Pave Low. To: The CV-22B replaced the MH-53 Pave Low. 2603:7081:3E07:782B:7989:A821:55C7:21C5 (talk) 02:05, 21 March 2022 (UTC)


 * Not needed. All the production V-22s have the B variant letter. -Fnlayson (talk) 18:26, 10 December 2022 (UTC)