Publications: 82 | Followers: 0

Low Level Rules of Conduct (ROC) - cnatra.navy.mil

Publish on Category: Birds 0

VT-35 Low Level Standards(Planning)
Entire Route shall be conducted in Combat Spread with exception of IP inbound or at discretion of the flight lead based on METT-THolding Areas (HA’s) shall be planned for and named after a female with first letter in congruence with cardinal direction in relation to the Objective Area (i.e. “Wendy” for HA west ofObjArea)left turns, 5NM legsAnchored off of the point prior to the IP or off of an identifiable terrain featureInitial Point (IP’s) shall be named after a vehicle make or modelwith first letter in congruencewith cardinaldirection in relation to the ObjectiveArea (i.e.“Subaru”forIP south of theObjArea)Utilize “minute plus” when planning timing from IP to LZ (to account for slowdown)ESA: 1000’ above highest obstacle for the ROUTE (w/in 25NM)MSA: 500’ above highest obstacle for the LEG (w/in 5NM)A/ATacanshall be assigned as follows:Flight Lead’s personalcallsignnumberDash-2 and Dash-3, 63 off of Lead’s number(i.e. – Lead: 62Y, Dash-2: 125Y, Dash-3: 125YMission Statement shall contain the 5 W’s, and choose from one of the following assault support mission types:Personnel insert or extractCombat ResupplyCommander’s intent on the mission page shall read:TACTICAL: Purpose andEndstateADMIN: “ProfessionalCompletion of all training events and scheduled flight hours, per the flight schedule, utilizing proper ORM.”Page Numbers shall be on all pages of smart packMSAs for each leg shall be inserted in the “FRQ” column of the form-70Turn points are planned to be flown over not flown byVertical profile slide after orientation (will be shown in the class)
Objective Area Diagram Shall contain the Following:Name ofOADIPPush timeL-hourLZcomminfoAsset V-diagramSun AZ/ELVNorth arrow/compass roseWind arrow with predicted winds typedoutMGRS andLatLongfor IP, LZ
VT-35 Low Level Standards(Planning – Objective Area Diagram)
LZ diagram shall contain the following:Name ofLZLZ information (size, description, MGRS andLatLong,etc)LZcomminfoIngress headingarrowEgress headingarrowWaveoffdirectionarrowSun AZ/ELVNorth arrow/compass roseWind arrow with predicted winds typed out
VT-35 Low Level Standards(Planning – LZ Diagram)
Cover PageNavLog(AF form 70)Stick diagram – ensure you check it over for changes8 ½ x 11 OAD8 ½ x 11 LZ DiagramACEOI upside down and backwards (when available)
VT-35 Low Level Standards(Planning – Smart pack)
Mission Fuel-The MINIMUM fuel required to fly the planned mission and land within NATOPS, SOP, and CNAF mins.Bingo Fuel- Fuel required from the furthest point on the route direct to the nearest approved refueling location (KNGP, KCRP, KSAT, KVCT) and land within NATOPS, SOP, and CNAF mins.
VT-35 Low Level Standards(Planning –Fuels)
VT-35 Low LevelStandards(Briefing)
Time-Hack will be conducted directly after introduction, at the next available minute. The time shall be obtained from the Naval Observatory website:http://www.usno.navy.mil/USNO/time/display-clocks/simpletimeORIENTATION:Define the boundaries of the AO (North, East, South, West) utilizing definable features such as MSRs, Northing/Easting, Bodies of water/prominent terrain featuresBrieflydiscuss overall terrainlay-down, Winds/Sun,prominent civilian built-up areas, ESAfeature, routes, objectivesCONOPS:Brief the “Big Blue Arrow” from takeoff to ENDEX in <60 seconds. Save the details for SOM.SOM:“Walk the dog” TBS-style. Do not gloss over the threats on leg slides. Discuss mitigation at first point of probable EN contact.Briefing Turn point: Brief the turn not amaneuver at the turn point.Brieftheentire brief Tactical first THEN clean up all the ADMIN items at the end of the brief.Do not use ambiguous descriptors such as: maybe, about, should, approximately,kindof, “that’sgottabe it”, “we are going to pass a town”, etc.Spend most of your briefing efforts on the Objective Area Diagram (OAD) and the LZ DiagramAs a technique, utilize God, Man, Mission concept to build the picture of describing the Objective Area and the LZ
VT-35 Low LevelStandards(Execution: Ramps up call)
Lets lead know you are ready to continue (as in, my ramp is up so I am ready to launch). Passed over intra-flight when ready to taxi to hold short in the following format:-RAMPS UP-FUEL STATE-SOULS-ALPHA CHECK (this information is read directly off of the PFD when direct to the first point on the flight plan)-YARDSTICK CHECK-FENCED-IN (or with exceptions)-Ex:“Stingray 61 is RAMPS UP, 2 souls, 2400lbs, Alpha check to Pt Bravo 035 @ 21.7, good yardstick, Fenced-In (with exceptions.)
VT-35 Low LevelStandards(Execution: Fence Checks)
FENCE-INchecks shall be completed as soon as possible afterlaunch (or on deck prior to, with exceptions)based on the threat (oras briefed) to identify maintenance / ordnance discrepancies in preparation for missionexecution.Reportsystems malfunctions to lead using a“BENT”call and a plain-language descriptionof themalfunction.CompleteFENCE-OUT checks as threat and safety dictate, but no laterthan crossingthe airfield / FOB / FARP boundary.These checks can be completed prior to departure with exceptions (Weapons, ALE,etc).Fire controlN/AEmissionsA/A TACAN set per briefRadAlt(Set 10% below – 450AGL)Lights (Navon)IFF as appropriateNavigationMFD SetupObstacles turned on at the 10 mile with 5 NM for labelsTerrain inhibit -exceptionSecond route loaded in the secondary flight planESA shall be input into theBaroAltminimums under “REFS”CommunicationRadiosset (V/UHF ready to go to manualfreqper brief) -exceptionExpendablesN/A
VT-35 Low LevelStandards(Execution: Legs)
Actions at/after each turn point:Hack clock once wings levelCheck winds/reset GSSpin new MSA into PSA and brief feature’s locationBrief what the next checkpoint is (Road bend, bridge, etc.)Then, update features as required
VT-35 Low LevelStandards(Execution: Navigation)
Primary navigation responsibility rests with the flight leader. All aircrew shall support theFlight Leadand challenge any perceived navigationdeviationwhen briefed Magellan parametersare exceeded. Automated navigation systems will be cross-checkedwithdeadreckoning.Columbusprocedures. Deliberate navigational deviations shall be preceded withtheproword“COLUMBUS” and the direction and distance of the deviation from a checkpointor keyterrain feature.Magellanprocedures. Unplanned navigational deviation shall be challenged withtheproword“MAGELLAN” followed by a steer(azimuthand distance) to the briefed course lineor thenext checkpoint.Criteria in which to announce“MAGELLAN”Unannounced deviation from route by 5nm±2minutesOverflightof the checkpointwithout appropriateturn ormaneuverClock to chart to ground method will be utilized primarily for Sim Events. Second Sim event will begin to demonstrate the utilization of the avionics (MFD, PFD, 120 Map Mode, FMS for timing,ProgPage,etc)First flight event will utilize clock to chart to ground with light reliance on the avionics available but have a basis of understanding for the following two events.Second and third flight event will utilize primarily the avionics in conjunction with the printed chart
Flight will be conducted in restricted airspace, MOA, MTR or as approved by Wing / MAGTF CommandersBrief minimum airspeed and altitudeWingman is always responsible for separation anddeconflictionWingman will not fly step-down when lead is 500’ AGL or belowAfter a “Knock it off” call, all aircraft in the flight will roll wings level and establish a climb to a pre-briefed altitude (MSA and MSA +500)All Aircrew will “Knock it off” if any of the following occurAny aircraft descends and remains below the minimum briefed altitudeAny aircraft descends in a turn that was intended to be levelAny aircraft becomes No Radio (NORDO) or loses Internal Communications System (ICS)Any aircrew loses Situational Awareness (SA)An interloper enters the flightAny unsafe condition observed by any crewmemberFollowing “knock it off”, Low Level training will not be resumed without verbal communication from all aircrew in the flightMore than one flight may operate on a Low Level route simultaneously provided the followingA common frequency is monitored by each flightEach flight has their own discrete frequencyFlight separation along the route is pre-briefed
The following is to be read VERBATIM at the completion of every brief
VT-35 Low Level StandardsLow Level Rules of Conduct (ROC)
Two separate threats for each day’s flightsMGRS and type of threat (SA-7, ZSU-23-4,etc)RoutesOther mission assets (AH/UH, FW, ISR, ETC)
Planning items assigned to students

0

Embed

Share

Upload

Make amazing presentation for free
Low Level Rules of Conduct (ROC) - cnatra.navy.mil