Jump to content

The website is under maintenance - To keep up to date of the current status, please read more here. Normal forum functions should resume over the next few weeks.

Sign in to follow this  
Force_Majeure

UOAF Event Standard Lineup & Coord Card + Briefing Skills

Recommended Posts

The purpose of this thread is to introduce a standard lineup and coord card for event use and to improve UOAF briefing skills. I would propose by gentleman's agreement that UOAF fraggers complete as much as the Coord Card part as possible and post a screenshot of it in the event thread or in discord for ambitious pickup games. Any other data is bonus, to include the plots and subplots. UOAF attendee pilots are not required to use it, but a copy of the Coord Card should at least be made available. The purpose of the Coord Card is that a 2-5 min review would cover everything that would be stated in the legacy package brief that can take up to 45 mins. The Coord Card was designed to take 2-5 mins to make.

 

UOAF MISSION CARD v25.69 DOWNLOAD

 

ybANTUm.png

 

I had some time to dote on the briefing culture here that I helped form before I did this for a living and I would like to standardize some things. Main point, I want to maximize in flight briefing time and minimize package briefing time. First, the earlier we can get a package commander, the better. I'd like to see a package commander volunteer a day or two before instead of during the event. That way a plan and brief can be made if desired.

The first part of a brief is the "Coordination Brief," introducing threats, frequencies, flight contracts, altitude deconfliction (if required), and contingencies. Every member of the package is present and listening to the package commander. IRL If some players are taking off from a different base, a "product" or packet of useful information like comm plans and maps is used instead. The "Coordination Brief," or "Coord Brief" presents usually 2-3 meeshun objectives and discusses the details of included products. For the purposes of BMS, minimum products would be the Coord Card and a .ini file for threat rings. Things like a screenshot of the map with flight plans is helpful, not required. Next, a brief AO description takes place identifying factor friendly and enemy order of battle, as well as factor threats (SAMs). A comm plan is introduced, usually by finger dragging the coord card. Next, the package commander will quickly and briefly identify contracts for the various flights. An example would be, at "18:00:00L or STEER 4, Hawg flight will descend to 500 AGL and ingress the target area. At 18:30:00L, package is miller time." The package commander's job is to NOT MICROMANAGE TACTICS, but rather to make package level decisions. If altitude deconfliction is needed at anytime in the sorty, it's discussed now. The final briefing point is contingencies, such as loss of assets and weather. At this point, pending no questions relevant to the package, the flights break into their individual flight briefs.

 

This is what an actual IRL flight brief board looks like, starting from the top left to bottom right:

0CsMPA7.png

 

A flight brief discusses flight objectives, threats, weapons, contracts, and tactics. Think of the left side as all the shit you do on a day to day basis. In fact, we literally brief most of this as "standard", meaning there are published squadron standards that everyone knows. As you move right along the board, you start discussing shit more relevant to the fragged meeshun at hand. For us, we actually draw out some attacks at the end of the flight brief. For the purposes of UOAF, I would talk through at least one attack and ask the wingmen questions about what they are supposed to do to confirm receipt of knowledge. Once the flight brief is complete, players will rejoin a channel. This is the first and last time that a "committee" session is held where flight leads and the package commander can discuss the meeshun in the presence of everyone. Do IVC checks, take a break, then fly.

 

A few notes, Strat SAMs (SA-2, 3, 6, 10, 11) should be given a letter and numeric identifier so that the SEAD package can identify a SAM that everyone knows, "MAGNUM KA-69". If there is only one SA-2 in the AO then "Magnum SA-2" is easier. Just do what's easier. An abort range should be given for every air threat and possibly published for a recurring event series. To abort means run away at MAX. When I say contracts, I'm referring to how collective flights or wingmen use radios, how they share information, maneuver their aircraft, and execute the mission. IRL we have precanned "contracts" so we don't have to brief individual maneuvers. Think of it as a playbook.

 

Congratulations, you are all now 69% arcade.

 

Force

 

 

Edited by Force_Majeure

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...