Author Topic: FSO: Operation Husky - Frame 2 Results  (Read 3866 times)

Offline DmdJJ

  • Copper Member
  • **
  • Posts: 183
Re: FSO: Operation Husky - Frame 2 Results
« Reply #30 on: June 13, 2009, 11:44:34 AM »
Why no points deduction for the Axis not hitting 110 within the first hour?
DmdJJ   
"The Damned"
"Damned if we do, no fun if we don't"
FSO Squad 412th FNVG
Target Rebaul-----> VMF-214   Fjord Fury RAF----> 315 Squadron

Offline DH367th

  • Aces High CM Staff
  • Nickel Member
  • ***
  • Posts: 771
Re: FSO: Operation Husky - Frame 2 Results
« Reply #31 on: June 13, 2009, 11:46:46 AM »
This is going to get out of control axis got a free run on lvts allied got a free run on 56 why dont we let scores stand and let frame 3 decide this?
You don't have to be crazy but it helps

Offline PFactorDave

  • Platinum Member
  • ******
  • Posts: 4334
Re: FSO: Operation Husky - Frame 2 Results
« Reply #32 on: June 13, 2009, 11:48:43 AM »
Maybe this is already known, maybe not.  332nd was assigned A47, we went in 24 strong in JU-88's. Kermit's squad did best they possibly could <S>, they were 8 strong I believe. That was all the escort we had, 1 squad was no show  :frown:. Can't help but believe they would have made some difference. It got ugly quick once we made contact with allied spits.

You had the misfortune of being assigned the base where all of the GV guys were allowed to spawn in fighters at T+50.  So, in addition to the fighter CAP that was assigned there, you ran into about 40 extra pilots.   All of whom were a little pissed and out for blood after the LVT disaster that we were put into.

1st Lieutenant
FSO Liaison Officer
Rolling Thunder

Offline DMBEAR

  • Persona Non Grata
  • Silver Member
  • ****
  • Posts: 1044
      • JG2 Richtofen
Re: FSO: Operation Husky - Frame 2 Results
« Reply #33 on: June 13, 2009, 11:49:31 AM »
This is going to get out of control axis got a free run on lvts allied got a free run on 56 why dont we let scores stand and let frame 3 decide this?

I think clarification only helps in the long run rather than just shrugging and ignoring it.

Offline ghostdancer

  • Aces High CM Staff
  • Platinum Member
  • ******
  • Posts: 7562
Re: FSO: Operation Husky - Frame 2 Results
« Reply #34 on: June 13, 2009, 11:53:57 AM »
Clarification is that written objectives said A57 while the map said A56. Neither CiC spotted my mistake and asked for clarifications. This is a CM mistake, mine, and not a CiC or squads involved mistake.

Fortunately both sides did see combat and had action up in the A56 area. The issue is the bombing results which is what I am considering and consulting with those involved.
X.O. 29th TFT, "We Move Mountains"
CM Terrain Team

Offline DMBEAR

  • Persona Non Grata
  • Silver Member
  • ****
  • Posts: 1044
      • JG2 Richtofen
Re: FSO: Operation Husky - Frame 2 Results
« Reply #35 on: June 13, 2009, 11:58:32 AM »
Clarification is that written objectives said A57 while the map said A56. Neither CiC spotted my mistake and asked for clarifications. This is a CM mistake, mine, and not a CiC or squads involved mistake.

Fortunately both sides did see combat and had action up in the A56 area. The issue is the bombing results which is what I am considering and consulting with those involved.

It wasn't a mistake to defend 57.

It was a mistake to attack 56.

Trusting a map with no key is the only mistake IMHO.

Of course, I was axis.  :devil

Offline j500ss

  • Nickel Member
  • ***
  • Posts: 495
Re: FSO: Operation Husky - Frame 2 Results
« Reply #36 on: June 13, 2009, 12:01:58 PM »
You had the misfortune of being assigned the base where all of the GV guys were allowed to spawn in fighters at T+50.  So, in addition to the fighter CAP that was assigned there, you ran into about 40 extra pilots.   All of whom were a little pissed and out for blood after the LVT disaster that we were put into.

Yep, your correct Dave, but we only had 8 escort to begin with. The squad we were missing is a fair size squad. Not saying it would have made a d** bit of difference, but more is always better  :lol

 :salute

Offline ghostdancer

  • Aces High CM Staff
  • Platinum Member
  • ******
  • Posts: 7562
Re: FSO: Operation Husky - Frame 2 Results
« Reply #37 on: June 13, 2009, 12:03:31 PM »
True DMBEAR .. but actually the written objectives were the mistake on my part. I meant for A56 to be the actual objective.
X.O. 29th TFT, "We Move Mountains"
CM Terrain Team

Offline ghostdancer

  • Aces High CM Staff
  • Platinum Member
  • ******
  • Posts: 7562
Re: FSO: Operation Husky - Frame 2 Results
« Reply #38 on: June 13, 2009, 12:04:07 PM »
Will look into when A110 was attack .. within T+60 or after.
X.O. 29th TFT, "We Move Mountains"
CM Terrain Team

Offline ghostdancer

  • Aces High CM Staff
  • Platinum Member
  • ******
  • Posts: 7562
Re: FSO: Operation Husky - Frame 2 Results
« Reply #39 on: June 13, 2009, 12:08:16 PM »
Yes, the axis attack on A47 was badly hurt by a squad escorting them being a no show. The Axis attack on A103 and A114 had a little more than 1 escort fighter per bomber. The axis attack on A47 had 0.36 escorts per bomber of 9 escorts and 25 bombers. This played a very big role on how things played out there and also highlight that is is very, very important for all squads in this event to actually turn out. A no show can have some very disastrous results and ruin the fun of another squad .. in this case the 332nd were butchered even with the herculean effort of the ~~~The Killuminati~~~ (the escort squad that did show up) defending them.
X.O. 29th TFT, "We Move Mountains"
CM Terrain Team

Offline Flifast

  • Copper Member
  • **
  • Posts: 311
      • Claim Jumpers
Re: FSO: Operation Husky - Frame 2 Results
« Reply #40 on: June 13, 2009, 12:08:24 PM »
I show A56 was the target on or spreadsheet and maps and wished we had a closer target.  We could have finished off that last fuel bunker and got back to rearm.  I see on the 6-7 target was listed as A57 and the 9th A56 and the 10th map details to A56.  Sorry about your airfield, better build a new one.  Fli

Chappy, still going hunting with us in Nov?  I look forward to walking the fields with you.  Tom
952-210-7245
Fliifast@msn.com

Offline ghostdancer

  • Aces High CM Staff
  • Platinum Member
  • ******
  • Posts: 7562
Re: FSO: Operation Husky - Frame 2 Results
« Reply #41 on: June 13, 2009, 12:22:38 PM »
In regards to C110 it was attacked before the T+60.

First spawn of the night was an Axis M8 by captdan at 22:03:09. First damage done to a ship of C110 was at 23:04:09. So they hit it at T+59 according to damage logs.
X.O. 29th TFT, "We Move Mountains"
CM Terrain Team

Offline DH367th

  • Aces High CM Staff
  • Nickel Member
  • ***
  • Posts: 771
Re: FSO: Operation Husky - Frame 2 Results
« Reply #42 on: June 13, 2009, 12:23:22 PM »
you know ghost as I was eating lunch I do feel both chappy and I share some blame for NOT asking 56 or 57 as allied cic I will stand by your
judgement on this I really dont care about score claim jumpers did as I ordered :salute stampf 11 miles you had every chance to engage
and didnt you had same map you knew 56 was a possible target you decided not to engage as 367th co if roles were reversed we would not let any bomber to either field we can play this game all day long I wont chappy axis  :salute great frame allied  :salute good job by all
look forward to frame 3
You don't have to be crazy but it helps

Offline Stampf

  • Plutonium Member
  • *******
  • Posts: 11491
Re: FSO: Operation Husky - Frame 2 Results
« Reply #43 on: June 13, 2009, 12:33:31 PM »
you know ghost as I was eating lunch I do feel both chappy and I share some blame for NOT asking 56 or 57 as allied cic I will stand by your
judgement on this I really dont care about score claim jumpers did as I ordered :salute stampf 11 miles you had every chance to engage
and didnt you had same map you knew 56 was a possible target you decided not to engage as 367th co if roles were reversed we would not let any bomber to either field we can play this game all day long I wont chappy axis  :salute great frame allied  :salute good job by all
look forward to frame 3

Dh,

Don't get me wrong sir.  I am also fine with whatever Ghostdancer decides.  It was an honest error by all involved.  As far as engaging a superior force - had they went for A57, (the valid target, we believed at the time), then of course we would have engaged at altitute, but when they turned north, (toward what we believed was a wrong target), we saw it as a chance to even the situation up a bit, by letting them get low and engaged in their attack before running in on them.  Also...we did not have 11 miles of pursuit.  More like 1 mile.  At 25k, the targets (both of them), were basically right below us.

IMHO, any commander who jeopardises the lives of their flight, for the sake of engaging alone is bonkers.  We had 14 obsolete planes against 24 enemy rides.  The clear choice under the given (albeit erroneous circumstance), was to let them dive and then engage.

But...like I mentioned earlier - We all lead as we see fit.

At least we all saw action and had fun.

 :salute
- Der Wander Zirkus -
- La Fabrica de Exitos -

Offline DMBEAR

  • Persona Non Grata
  • Silver Member
  • ****
  • Posts: 1044
      • JG2 Richtofen
Re: FSO: Operation Husky - Frame 2 Results
« Reply #44 on: June 13, 2009, 12:34:54 PM »
you know ghost as I was eating lunch I do feel both chappy and I share some blame for NOT asking 56 or 57 as allied cic I will stand by your
judgement on this I really dont care about score claim jumpers did as I ordered :salute stampf 11 miles you had every chance to engage
and didnt you had same map you knew 56 was a possible target you decided not to engage as 367th co if roles were reversed we would not let any bomber to either field we can play this game all day long I wont chappy
axis  :salute great frame allied  :salute good job by all
look forward to frame 3

Thats BS.  They were assigned a target to defend and did so.  There could have been other planes going A57 as well.   

Quit making it sound like they were doing anything less than that. 

 :salute JG11 you defended your target per frame II objectives.