|
Note: You must be registered in order to post a reply.
|
| T O P I C R E V I E W |
| Vosene |
Posted - 10 Jan 2016 : 21:54:03
Flight leads in this Sunday's official campaign mission, "Korean 4.33 Part 7" are requested to post a debrief of their flights actions, including any lessons learned or that should be learned by others.
Please put the following information at the top of your post:
Flight Role: (SEAD, ESCORT, STRIKE, Etc..)
Callsign11: "Pilot's name" AA=X AG=X RTB,MIA/KIA,EJT
Callsign12: "Pilot's name" AA=X AG=X RTB,MIA/KIA,EJT
Callsign13: "Pilot's name" AA=X AG=X RTB,MIA/KIA,EJT
Callsign14: "Pilot's name" AA=X AG=X RTB,MIA/KIA,EJT
Mission Outcome: MS/PS/MF
|
| 7 L A T E S T R E P L I E S (Newest First) |
| Floyd |
Posted - 17 Jan 2016 : 17:09:14
Oops, a typo. I've meant 18:50 UK, that is 19:50 German time.
Sorry about that. |
| Ghostrider |
Posted - 17 Jan 2016 : 14:46:32
thx Floyd. Means 20.50 Swiss&German time, right? ;) |
| Floyd |
Posted - 17 Jan 2016 : 13:52:43
I'll be there at 19:50 UK. |
| Ghostrider |
Posted - 17 Jan 2016 : 13:12:30
Not the proper place, i know. But i like to try a connection test tonight and, if possible, join the flight. can someone show up a bit earlier tonight to perform a connection test?
thx in advance
ghosty |
| Sharpe |
Posted - 12 Jan 2016 : 14:29:04
Fury 3: SEAD
Outcome: MS
Fury31”Sharpe”. AA0/AG2. RTB.
Fury32”Vosene”.AA0/AG0. RTB.
Fury33”Poppy”.AA0/AG13. RTB
Fury34”Zipgun”.AA0/AG8. RTB
Fairly simply flight, but complicated delivery profile. 1 and 2 were armed with HARM, tasked with supressing pop up SAM threats near the target. 3 and 4 were armed with SDB and tasked with the destruction of known fixed SAM installations (including the Frigate task group).
As the flight ingressesed 3 and 4 were released to deploy their ordnance (the time of flight of the stores meant strike flight had to be 20nm behind SEAD and escort to allow time for weapons effect and BDA). Once BDA showed the SAM threats as clear, strike flight was called in to hit main target.
A complicated mission (in terms of weapons delivery) that was executed very well by blue flight. Well done to all.
Notes:
Package coms were appalling to begin with. If the package commander is having tech issues this needs to be addressed immediately (ie on the ground before the package takes off if possible), not 20-30 mins into the flight after being pressed by other flight leads. In this case, the strike flight was over 40 miles out of position with the lead flights close to the FLOT before any mitigation was taken to rally the package, and none of this was at the direction of the package commander. This highlights the need for a package 2IC to be nominated during the briefing so there is a clear cadence on who takes over and when.
-Sharpe
 |
| Syringe |
Posted - 10 Jan 2016 : 22:31:09
Flight Role: OCA Strike
Falcon31: "Sabre" AA=0 AG=0 Tech
Falcon32: "Mango" AA=0 AG=0 Ejt
Falcon33: "Syringe" AA=0 AG=3 RTB
Some of CTDs and problems with comms delayed Our take off.
Sabre throw lead on me. When Mango and I was descending Mango make some over-G turn and hang bombs.
He was downed by SA-7 when attacking runway.
My bombs destroyed one runway.
|
| Veiland |
Posted - 10 Jan 2016 : 22:19:54
Flight Role: ESCORT
Lobo31: "Veiland" AA=0 AG=0 RTB
Lobo32: "Elmp" AA=0 AG=0 RTB
Lobo33: "Floyd" AA=0 AG=0 RTB
Lobo34: "Griffin" AA=0 AG=0 RTB
Mission Outcome: MS
Besides comm problems and the crash we had in Lobo3 it was really very uneventful.
Only contacts we picked up on radar was SU-25's which was ignored.
On the leg home we set up for a ILS landing, but it turned out we could make a visual approach. |
|
|
| 185th VFS |
© 2000-2018 185th VFS |
 |
|
|
