FDC
TROUBLESHOOTING CHECKLIST
STEP ONE: (SURVEY CHECKLIST)
_____ Do you have common survey (common direction and grid)?
_____ Do you have common grid between the battery and target area to include OP's and known points?
_____ If you do not have survey, have you registered to account for location error? (see step 4.)
_____ If survey is unavailable, conduct hasty ASTRO before grid.
_____ If SCP is available conduct directional traverse before grid.
_____ BC establish position IAW white paper (Avg Mode; common postion)
_____ Verify database:
_____ Verify AFU; Update information:
_____ Azimuth of lay.
_____ Propellant temperature.
_____ ORSTA (Aiming circle location).
_____ ST (Field for proper sight).
_____ WPN.
_____ MODEL.
_____ DF (Deflection of 3200).
_____ Verify BCS; Pieces:
_____ Do coordinates correspond to actual locations on the ground or map?
_____ Did you use verification method? (i.e. M17 plotting board)
_____ Was polar data entered correctly?
_____ Did you have to change ORSTA for any reason? If so, did you delete and re-enter pieces?
_____ Did you have to change a piece location for any reason?
_____ If so, did you delete and re-enter pieces?
_____ Verify AFU; AMMO information:
_____ Projectile weights.
_____ Propellant lots the same in computer as on the guns.
_____ Verify SPRT; MAP information:
_____ Are the long coordinates correct?
_____ SPHEROID.
_____ GZ (Grid Zone).
_____ GD (Grid Declination).
_____ Map Datum.
_____ Verify Target Location:
_____ What method of target location was used?
_____ Check grid and altitude.
_____ If polar, check OB and OB coord/ALT.
_____ If shift, check known point coord/ALT.
STEP TWO: (MET CHECKLIST)
_____ Verify the database:
_____ Verify SYS; SET UP
_____ Position and DT1 for space and time validity.
_____ Check MET line data. Suspect any keystroke errors?
_____ Does MET match actual weather conditions?
_____ Overload lines of MET/Standard lines of MET?
_____ Station heights?
_____ Are all units on the same MET?
_____ Have correct concurrent MET procedures been performed?
_____ If MET is bogus, consider registering to account for weather conditions or request new MET.
STEP THREE: (MUZZLE VELOCITY MANAGEMENT CHECKLIST)
_____ Are MVV's stored for the projectile family and propellant model being fired?
_____ Verify BCS; MVV file for each gun
_____ Where did muzzle velocity variation come from?
_____ If historical data:
_____ Is manufacturer's lot on piece same as in MV record log?
_____ Is data inferred?
_____ If M90 chronograph data:
_____ Have MVCT 90-2 corrections been applied?
_____ Does BCS MVV check with BUCS MVV?
_____ Is lot on piece the same and being used?
_____ Is a preferred charge being fired?
_____ Use wear tables and experience to see if MVV's make sense. Let observers assist in verifying shooting strength.
_____ Are the MVV books at battery and battalion updated?
STEP FOUR: (REGISTRATION CHECKLIST)
_____ Check registration file. Does AFU; REG exist for the position? Propellant lot? Charge and trajectory being fired?
_____ Are the registration corrections suspect? Is database considered good and large REG corrections reflected?
_____ Shoot a mission to MET gauge point with data prior to registration and compare data with the mission shot with registration.
_____ Were observer techniques correct?
_____ Was the registration validated using work around techniques?
_____ Has the concurrent MET procedure been performed (MET/REG)? If so, was the work around to validate been performed?
_____ Has the updating of survey taken place (SURV/REG)? If so, was the work around performed?
_____ Did the piece measure the azimuth at the end of the registration?
_____ If registration corrections were transferred to you:
_____ Do you have common survey?
_____ Was the AFU; REG received after the concurrent MET was performed?
_____ Do you have a valid MET?
_____ Do you have MVV data? If not, are you firing the same lot as the registration battery?
_____ Consider deleting or re-registering.
Table
of Contents
FDO
and Chief Computer Safety Checklist
Howitzer
Direct Fire Range Card
NEWSLETTER
|
Join the GlobalSecurity.org mailing list |
|
|