| Author |
 Topic  |
|
|
Ironman
UNITED KINGDOM
604 Posts
Status: offline |
 Posted - 08 Mar 2015 : 22:19:16
|
Python Flight
Ironman 0-0 RTB MS
Poppy 0-0 Tech MS
Homer 0-1 RTB MS
Tank 0-1 RTB MS
Lost Poppy at take off(tech), Tank had comms problems - finally sorted before we got to our IP.
Held off 20 miles west of target area as instructed by PC.
Finally made run in (GATE) with mixed, if not dubious results, - no losses to flight and we were out of target area (RTB) when server crashed.
good flight - good comms - good PC.
Back to Korea - please !!!!
Ironman
|
|
|
Homer
United Kingdom
1082 Posts
Status: offline |
Posted - 09 Mar 2015 : 07:14:43
|
Strong DPRK please...
I heard Ironman's "GBUs away" upon release, but no sign of them on the ACMI. I did see lots of smoke also from the runway as well as the depot when I was loitering waiting for Tank to rejoin.
On Tank, most impressive from a "newbie", good comms and good formation flying. On Ironman, he is the second best flight lead I've had in all the time I been flying 185th, good comms left me in no doubt what he wanted all the time, and his flying was always on target speed and alt which made staying in position much much easier. Sorry we lost Poppy at take-off, the engine techs will be getting their butts kicked no doubt...
Strong DPRK please... |
 |
|
|
Elmo
UNITED KINGDOM
238 Posts
Status: offline |
Posted - 09 Mar 2015 : 07:14:57
|
Flight Role: SEAD Escort
Serpeant51: "Elmo" AA=2 AG=1 RTB
Serpeant52: "Floyd" AA=0 AG=1 RTB
Serpeant53: "Griffin" AA=2 AG=2 RTB
Serpeant54: "Veiland" AA=0 AG=1 RTB
Mission Outcome: TBC not sure due to 2 losses in package
Flew to target, called to Shark that they were lead flight into area, had good comms from them letting us know the area was clear.
First element went in to target and no. 2 got a shot at ground threats, both 1 and 2 then went defensive against a pop up SA11 South of target.
3 and 4 pushed in and between them got 3 shots at air defenses before turning cold.
1 and 2 then pushed back to target with 2 getting his last shrike away and 1 engaged two Mig29S.
3 and 4 then pushed back in and engaged two SU25's with 3 getting both kills and 4 firing off his last shrike.
I then heard strike packages saying they were going to push the target which I denied as the picture was a little murky and still lots of SA11 and SA13.
I believe other AI flights in the area took out some other A-A targets which I could hear being called but could not get a confirmed lock on radar. I flew in and got my two shrikes off then gave the picture to strike flights and called them in.
Good comms in our flight and all round to be honest, had a pretty good picture of where everybody was.
The target area is still very saturated with SA11 and SA13 so if we are to continue this campaign we need to keep on flying the SEAD role heavily to clear the area.
Elmo |
|
|
|
Sharpe
UNITED KINGDOM
638 Posts
Status: offline |
Posted - 09 Mar 2015 : 08:58:38
|
Falcon 5 (Deep Strike)
Mission Outcome MS (I think???)
Falcon 51 Sharpe 0-1 RTB MS
Falcon 52 Simpson 0-0 RTB MS
Falcon 53 Sabre 0-0 RTB MS
Falcon 54 Mango 0-0 RTB MS
Took off in good order and proceeded to target. Flight took a long time to rally despite deliberately slow take off and cruise.
As we closed to the target area it was clear the SEAD aircraft were very busy (good package comms guys). As we closed to the IP we called our attack and were immediately waved off by the package commander due to SAM activity so we entered an orbit near the IP to await instructions.
Package commander stated that the primary target area might have been ok to strike but the secondary site was not looking safe due to extensive SAM cover but that it was up to the flight leads in both cases. Upon hearing this, lead decided to make a single pass at the power station (primary target for deep strike) to assess the extent of the SAM cover. While weapons delivery was successful the target area was to hot for extensive attack so RTB was ordered with the area becoming hot.
Not long after this point the game crashed.
Learning points from flight:
1) Intra flight comms was very poor. Remember to reply in sequence 2/3/4 (and quickly). Don’t jump in, and don’t leave dead air on the coms and don’t make the flight lead ask the question again. If you are doing something say ‘standby’.
2) Sabre had extensive comms issues during the briefing and the flight (TS and IVC) that he will need to look into as this caused him to miss several critical communications (both in briefing and in flight).
3) Chatter (especially when it cuts over Uniform comms) is not acceptable, especially when the cross chatter is pilots suggesting a bug out when the uniform chat is providing information that the flight lead needs in order to make an informed decision on that topic. Keep your ear open for uniform chatter; it’s not just for the flight lead ;)
4) The flight took far too long to rally – even with lead slowing to 280knts as we crossed the fence in point.
5) The above (learning) points aside, the flight performed very well in a complicated picture with extensive threat coverage.
6) Package comms (and command) was very good.
7) Members of my flight expressed concern at the stability of this map as a result of this crash and a crash last week, I agree with this concern.
8) I would also like to express concern at the validity of flying in a campaign where platform performance data has been heavily modified for no real reason and is way outside of practical realities. At least one (possibly two) of my flight reported being engaged by SA13’s when they were at or above FL250. This exceeds the performance parameters for that SAM system by double.
-Sharpe
 |
|
|
| |
Topic |
|
|
|
| 185th VFS |
© 2000-2018 185th VFS |
|
|
|
Sunday 08/03/15 BfB
