Matrix Games Forums

Forums  Register  Login  Photo Gallery  Member List  Search  Calendars  FAQ 

My Profile  Inbox  Address Book  My Subscription  My Forums  Log Out

F-35C first carrier landing

 
View related threads: (in this forum | in all forums)

Logged in as: Guest
Users viewing this topic: none
  Printable Version
All Forums >> [New Releases from Matrix Games] >> Command: Modern Operations series >> F-35C first carrier landing Page: [1]
Login
Message << Older Topic   Newer Topic >>
F-35C first carrier landing - 11/3/2014 10:38:14 PM   
Rudd

 

Posts: 1501
Joined: 7/10/2013
Status: offline
https://www.youtube.com/watch?v=STVAM85y3i0#action=share
http://news.usni.org/2014/11/03/u-s-navy-version-f-35-lands-carrier-first-time
Post #: 1
RE: F-35C first carrier landing - 11/3/2014 11:06:53 PM   
hellfish6


Posts: 843
Joined: 6/15/2008
Status: offline
And the Navy is just a little sad that it actually worked...

_____________________________


(in reply to Rudd)
Post #: 2
RE: F-35C first carrier landing - 11/3/2014 11:44:31 PM   
Vici Supreme

 

Posts: 558
Joined: 12/4/2013
From: Southern Germany
Status: offline

quote:

ORIGINAL: hellfish6

And the Navy is just a little sad that it actually worked...




_____________________________


(in reply to hellfish6)
Post #: 3
RE: F-35C first carrier landing - 11/4/2014 4:49:31 AM   
LoBlo

 

Posts: 82
Joined: 9/12/2014
Status: offline
On a semi-related note. I don't understand the way that Command models the F-35 DAS. Its an infrared system with 360 arc, but its modeled with 0nm maxed range. I don't get it. Shouldn't it be modeled with some detect range to it? Or is the system still to early in development to consider worth trying to interpret performance (or lack there of)?

(in reply to Rudd)
Post #: 4
RE: F-35C first carrier landing - 11/4/2014 9:02:09 AM   
Dutchie999


Posts: 117
Joined: 10/8/2014
Status: offline

Mixed feelings here. They should have build a naval F-22 variant. Especially the Navy with its carriers which is always close to the action should have an air superiority platform.

(in reply to LoBlo)
Post #: 5
RE: F-35C first carrier landing - 11/4/2014 1:31:38 PM   
jdkbph


Posts: 339
Joined: 2/11/2007
From: CT, USA
Status: offline
You mean in addition to the F35? No V/STOL capability with the F22....

JD

(in reply to Dutchie999)
Post #: 6
RE: F-35C first carrier landing - 11/4/2014 2:21:22 PM   
jtoatoktoe

 

Posts: 208
Joined: 10/9/2013
Status: offline

quote:

ORIGINAL: jdkbph

You mean in addition to the F35? No V/STOL capability with the F22....

JD

The Navy one doesn't either. The Marine Corps/British B model does though and could in theory be used on Carriers but in the Marine Corps will be mostly on the Assault Ships, but the C model(Navy) is just a larger stronger A model.

(in reply to jdkbph)
Post #: 7
RE: F-35C first carrier landing - 11/4/2014 3:36:18 PM   
jdkbph


Posts: 339
Joined: 2/11/2007
From: CT, USA
Status: offline
I'm aware. I was thinking in total... either - or, yeah?

The whole idea of the JSF was one airframe for all services, and then some. If you dropped the A and C model, you would still need a weapons systems program to produce the B. One way or another those development costs would be incurred. Add to that the cost of developing a navalized F22 and you're carving out a large piece of budget most likely targeted for other things... like maybe subs and surface combatants and carriers.

It's a great what if, but I don't think it's at all practical.

IMHO

JD

(in reply to jtoatoktoe)
Post #: 8
RE: F-35C first carrier landing - 11/8/2014 5:50:13 AM   
MR_BURNS2


Posts: 974
Joined: 7/18/2013
From: Austria
Status: offline
Am i imagining things here, or are they taking off without afterburner?

https://www.youtube.com/watch?v=APuYyfq12ts

_____________________________

Windows 7 64; Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz (8 CPUs), ~2.7GHz; 6144MB RAM; NVIDIA GeForce GTX 970;



(in reply to jdkbph)
Post #: 9
RE: F-35C first carrier landing - 11/8/2014 8:38:00 AM   
Dutchie999


Posts: 117
Joined: 10/8/2014
Status: offline
quote:

ORIGINAL: jdkbph

I'm aware. I was thinking in total... either - or, yeah?

The whole idea of the JSF was one airframe for all services, and then some. If you dropped the A and C model, you would still need a weapons systems program to produce the B. One way or another those development costs would be incurred. Add to that the cost of developing a navalized F22 and you're carving out a large piece of budget most likely targeted for other things... like maybe subs and surface combatants and carriers.

It's a great what if, but I don't think it's at all practical.

IMHO

JD


The conclusion from this interesting paper:

quote:

1. Aircraft designed by a single country are not necessarily more expensive than those developed through international cooperation.
Gripen and Rafale were both developed by single countries, but end up costing substantially less than Eurofighter, which is produced by a four-nation consortium.

2. But single-nation development does not guarantee lower costs, as the three US fighters all cost substantially more than the two European “national” fighters, and are comparable to those of Eurofighter, a four-nation cooperative program.
Conversely, the projected unit cost of the only (partly) cooperative US aircraft, the Joint Strike Fighter, already exceeds that of Gripen and Rafale and of two other US aircraft, F-18E and F-15E, all of which are single-nation designs.
3. Long production runs do not always lead to less expensive aircraft.

The F-18E, with a production run of 462 aircraft, costs half as much again as the Rafale, which has a much smaller production run of 294 aircraft. JSF will cost twice as much as Rafale, despite having a production run almost ten times as large, and half as much again as the F-18E, whose production run is five times smaller. All three are modern, multirole combat aircraft.

4. While charges for major program stoppages and restructurings add to program costs, the increase is not proportional to the length of the hiatus. Both Eurofighter and Rafale programs were halted and restructured, adding eight or ten years to their development cycle, while F-15E, F- 18E and Gripen were not, yet this is not demonstrably reflected by the difference in their respective cost.

5. Continuity in development is the best way to avoid cost overruns. Gripen and F-18E (the F-15E is not significant in this respect) are the only programs to have avoided lengthy “freezes” and large-scale re-designs, and their production costs are notably lower than competitors’. Program unit costs of Rafale, Eurofighter and F-22 exploded after they were “suspended” for several years for major re-designs or funding shortfalls.

6. Although these aircraft were all developed beginning in the late 1980s, and for broadly similar missions, there is no common ratio between R&D and acquisition costs. Indeed, there seems to be no correlation whatsoever between these costs, reflecting each aircraft’s unique R&D itinerary and development history.
In other words, development costs are influenced not by so much be an aircraft’s actual capabilities as by a “smooth” management and development history.


(Disregard the F-35 numbers in that paper. Probably way too low now)


Attachment (1)

< Message edited by Dutchie999 -- 11/8/2014 9:39:07 AM >

(in reply to jdkbph)
Post #: 10
RE: F-35C first carrier landing - 11/8/2014 12:50:02 PM   
jdkbph


Posts: 339
Joined: 2/11/2007
From: CT, USA
Status: offline
That is interesting. But I was referring to development costs. Dev costs can be spread out over the life of a program production run so that, all other things being equal (and I know they're not), the more you build the lower the unit cost. However, the development cost is still the same. It doesn't go up or down, whether you buy 10 units or a 1000 units. And that's what I was referring to. The point is that the F35 dev cost would be pretty much the same whether you buy as originally planned (lots of As, a bunch of Cs and a few Bs) or just buy a few Bs.

JD

(in reply to Dutchie999)
Post #: 11
RE: F-35C first carrier landing - 11/8/2014 2:27:10 PM   
Dutchie999


Posts: 117
Joined: 10/8/2014
Status: offline

quote:

ORIGINAL: jdkbph

That is interesting. But I was referring to development costs. Dev costs can be spread out over the life of a program production run so that, all other things being equal (and I know they're not), the more you build the lower the unit cost. However, the development cost is still the same. It doesn't go up or down, whether you buy 10 units or a 1000 units. And that's what I was referring to. The point is that the F35 dev cost would be pretty much the same whether you buy as originally planned (lots of As, a bunch of Cs and a few Bs) or just buy a few Bs.

JD


Yes that true of course. What I find very interesting is that the cost for research and development for the F-22 was $32 billion according to the GAO. And the current research and development cost for the F-35 stands at $61 billion (mid 2013). I understand that building a '3 aircraft in 1 frame' can't be easy but the basis for all the technology was there from the F-22. It was just building a less capable stealth aircraft, less capable radar, smaller internal weapons bay, less capable ELINT etc. The only new things were the cockpit displays, EOTS and DAS. I would have guessed that then the R&D costs would have been half of that of the F-22. Since there was basically all the work done and not double the R&D cost of the F-22.


(in reply to jdkbph)
Post #: 12
Page:   [1]
All Forums >> [New Releases from Matrix Games] >> Command: Modern Operations series >> F-35C first carrier landing Page: [1]
Jump to:





New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts


Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI

1.406