MARINE AVIATION

1
MARINE AVIATION MPF PRE-TAILORING CONFERENCE
WORKING GROUP 1 MALSP DOCTRINE- REQUIREMENT
DEF/RESOURCES
CAMP SMITH, HI 13-17 June 2005
2
WG 1 MALSP DOCTRINE- REQUIREMENT DEF/RESOURCES

• ISSUE 1-01 Define the Aviation MPF requirement.
• DISCUSSION The first step will be to Define FIE
  and RESP.
• FIE RESP Geo Pre Pos MPSRON
  (pre-positioning objective) Total Requirements
• FIE RESP will be determined using these
  assumptions
• Due to strategic lift constraints, the FIE has to
  be the minimum possible wt cube.
• 15 days of remote operations
• Flying a sustained sortie rate (per MSTP
  guidelines).
• CLASS IX(a) will constitute at least a 30 day
  block (FISP)
• Class V(a) will be pre-positioned.
• RESP arrives w/ FIE
• MPF augmentation arrives day 16
• MEF ACE will solve TR
• After FIE is defined, MARFOR and MEF ACE will
  determine the Appropriate MPF requirement
• MARFOR MEF ACE will validate data with wings.
• RECOMMENDATIONS For each T/M/S the model
  manager will define the FIE using
• the above assumptions and submit to 1st MAW. 1st
  MAW and MFP will determine
• total requirement and subsequently the MPSRON
  slice (pre-position objective) of the
• total requirement. Tasking will be assigned at
  the Wing conference July-05.
• This will be submitted for consideration for MPF
  MMC-9 tailoring.

3
WG 1 MALSP DOCTRINE- REQUIREMENT DEF/RESOURCES

• ISSUE 1-02 Define standard naming conventions
  (for TPFDD PID)
• MEU Ashore Dirt-Det
• RESP
• MPF Augmentation Support
• Global Preposition Assets
• FIE
• MALSP COMPONENTS (CSPs) FISP, PCSP, CCSP, FOSP
• DISCUSSION Standard nomenclature for ULN
  packages need to be established fleet wide IOT
  reduce confusion for deliberate planning. A
  standard naming convention will help planners
  understand the capability and purpose for a given
  ULN. This should be identical for a given T/M/S
  across all wings. In the past, naming
  conventions have been inconsistent between the
  wings.
• RECOMMENDATIONS We need recommendation from
  MARFORPAC defining the use of naming conventions
  for aviation ULNs. All G-5s need to concur and
  ASL will release message directing compliance.

4
WG 1 MALSP DOCTRINE- REQUIREMENT DEF/RESOURCES

• 1-03 ISSUE No doctrine exists for un-tethered
  MEU operations ashore
• DISCUSSION Recent extended MEU deployments
  ashore have demonstrated the need for
  augmentation other than that supplied from the
  ship, mainly AVCAL appropriate support
  equipment. Established doctrine for MEU planning
  does not include extended, over the horizon
  operations supported from the ship.
• Lack of ship space limits what MEU can pack for
  possible Ops Ashore
• SE/AWSE Dirt Det has been pulled first from
  Ship, MPF, garrison, Ground Prepo Gear, no set
  method.
• RECOMMENDATIONS The dirt det RESP/ capability
  set will need to be part of the MEU work-up IOT
  identify and have on-call.
• Assumptions for MEU include
• Plan for over the horizon ops in work-up
• Feet dry gt 15 days
• A FISP/SE (RESP) notional package is currently
  being developed by I MEF.
• Class V(a) air lift packages can be applied
• MWSS/MACG capability sets are being developed by
  HQMC ASL
• Recommend participation in tri-MEF exercise _at_
  BIC
• Implement BIC COT-LOT SOP currently in-work by
  MARFORs
• Establish METLs for off-load and incorporate in
  MEU certification

5
WG 1 MALSP DOCTRINE- REQUIREMENT DEF/RESOURCES

• ISSUE 1-04 Identify MCPP-N use in deliberate
  planning requirements.
• DISCUSSION It has been determined that
  equipment staged at MCPP-N cannot be used for
  deliberate planning purposes due to the political
  and bureaucratic complications (i.e. not assigned
  to any current OPLAN). It can, however, be
  considered for augmentation support, as it is
  currently being used. Marine aviation needs to
  consider the equipment stored therein and perhaps
  tailor that to a more useful set of equipment
  that can augment foreseeable contingencies.
• RECOMMENDATIONS MCPP-N 2nd MAW will determine
  the right mix of equipment to place in Norway and
  this will be validated by all wings and MARFORs.
  Coordination will be made by HQMC ASL.

6
WG 1 MALSP DOCTRINE- REQUIREMENT DEF/RESOURCES

• ISSUE 1-05 Identify actual players in notional
  MEB for MMC-9.
• DISCUSSION IAW the current MCB 3501, the
  following mix of aviation weapon systems are
  supported
• Current MCBul 3501
• F/A-18 36 A/C/D (one each)
• AV-8 16 Two eight plane Dets
• EA-6B 5
• KC-130 12 Six F and Six R Dets
• HMLA 9/18
• HMM 24 (Assume MEB will join a MEU, total 36)
• HMH 16 Two eight plane Dets
• New 3501 to be signed by end of CY 05
• RECOMMENDATION This document MCB 3501 will be
  reviewed once a year, MARFORs MCCDC make
  review. No anticipated changes this year.
  Enclosure 2 (MEU force list must be included).

7
WG 1 MALSP DOCTRINE- REQUIREMENT DEF/RESOURCES

• ISSUE 1-06 L Class Ship RRC (Readiness Review
  Conferences)/Tailoring
• DISCUSSION Lack of ship space limits what MEU
  can pack for possible Ops Ashore. SE/AWSE Dirt
  Det pulled first from Ship, followed by MPF,
  RESP, Ground Prepo Gear
• RECOMMENDATION HQMC ASL shall assign
  participants in RRC to ensure MEU requirements
  are met for success ashore.

8
WG 1 MALSP DOCTRINE- REQUIREMENT DEF/RESOURCES

• ISSUE 1-07 Determine the MEU slice on the
  MPSRON.
• DISCUSSION The ship containing the MEU slice
  (formally the Flag Ship) should contain the SE
  for aircraft assigned to a notional MEU
• CH-46 12 aircraft
• CH-53 4 aircraft
• AV-8B 6 aircraft
• AH-1 6 aircraft
• UH-1 3 aircraft
• Currently the MEU slice contains SE for the
  above and also includes 4 more CH-53s and an HMLA
  mix for 27 aircraft.
• RECOMMENDATION Tailor to the specific notional
  MEU on that ship and spread load the rest across
  the MPSRON.

9
WG 1 MALSP DOCTRINE- REQUIREMENT DEF/RESOURCES

• ISSUE 1-08 Aid deliberate planning and mitigate
  limited strategic lift capabilities by creating
  doctrine for global positioning in PACOM AOR to
  support current OPLAN/CONPLAN execution.
• DISCUSSION It may be prudent to consider
  pre-positioning some of the tailored MPSRON SE in
  the PACOM AOR IOT enable the War fighter swifter
  response to minimum warning scenarios. The past
  two conflicts have caused a crises planning
  dilemma WRT matching up the FIE with the MPSRON
  slice to give timely RSOI. This usually results
  in larger FIEs so the units can operate until
  MPSRON equipment arrives. Further resulting in a
  significant amount of unused SE.
• RECOMMENDATION Recommend the Wing planning
  conference (July 05) identify the desired MCPP-P
  for Marine aviation. Then the MPF working group
  can analyze implementation.