-
Landing Code Status
"Brevity Codes"
- Code 0 Ground AbortCode 1 No additional discrepanciesCode 2 Minor discrepanciesCode 3 Major Discrepancies
- Code 4 Radiological, Chemical, Biological
- Code 5 Battle Damage
-
Deviation Codes
- GAA - Before engine start, Mx
- GAB - After engine start, before taxi, Mx
- GAC - After Taxi, Mx
Ref: AFI 21-101 Table 4.3 Reports system status - after landing - Parking
-
Aircraft Recovery
- Aircrew departs - debrief
- DCCs safes aircraft
- Oil Samples - service & inspect
- Unscheduled/scheduled Mx
- Mx Repair Priority
- AFI 21-101 Table 1.1
-
Debrief
- End of mission or abort
- NO debrief req. w/ code 1 or code 2
- EXCEPT after last flight of the day
- MIS used enter flying time info.
- Ref AFI 21-101 Para 4.7
-
Debrief
- Documents:
- in-flight discrepancies
- Aborts
- Emergencies
- Flying time info.
- Ops checks
- # of flights
- FCFs
- Munitions Drops
- Repeats/recurs
- Deviations
- Fault Codes
-
Mission Preparation
- Adjust fuel loads
- Configure aircraft
- Load: munitions, flares, chaffs
-
Inspections
- -6 Ins = Crew chief
- Preflight
- Thru flight
- BPO
- Forms doc. ER/CR
-
Inspections
- -1 Ins = AircrewAircrew walk around
-
Aircraft Launch
- Engine start
- System Checks
- Marshaled Out
- EOR - Final Ins before take-off
- EVERYONE responsible for:FOD walks
- Req. Documentation
-
Red Ball Mx
- Sense of Urgency
- TWO hours prior to launch or until air crew release back to Mx
- Tech Data shortcuts or deviations ARE NOT authorized
- Status Changes - MUST re-accomplish another ER
- Red X discrepancies must be cleared in forms and MIS
-
Mx Ops Center (MOC)
- Coordinates ALL Mx actions
- Flightline, back shops, supply
- Pro-Super and Expediter communicate directly to MOC:
- Aircraft config. changes
- Ins, start and completion times
- MOC coordinates w/ outside agencies
-
Aircraft Status Ref.
- AFI 21-103, Equipment Inventory and Utilization Reporting
- MAJCOM Supplements to this AFI
-
Aerospace Vehicle Distribution Office (AVDO)
- Base/Depot Levels
- Maintains aircraft inventory
- Notifies MAJCOM of possession changes
- Reviews aircraft status (Mx/Supply)
- NOTE: PS&D
-
Aerospace Vehicle Utilization Monitor AVUM
OPS responsibility
- Base/Depot levels
- Establish/publish procedures for Ops/Mx
- Track/report flying hours and sorties
-
HQ AFMC AVDO
Maintains the MASTER AF Inventory
-
Aircraft Logistics Status Reporting
- Reporting Mx Status
- Use multiple status: means aircraft is broken for more than one condition
- Code describe capability based on DOC
-
Design Operational Capabilities (DOC)
-
Status Codes
FMC, PMC, NMC
- PMC/NMC add letter
- M - Mx
- S - Supply
- B - Both
- NMCM/NMCB needs MX code
- S- Scheduled
- U- Unscheduled
-
Mx Status Starts When?
In-flight discrepancies: times starts aircraft parks
Ground found discrepancies: time starts discrepancy is found
-
Mx Status Stops When?
- Mx completed IAW T.O.
- Ground Checks are C/W
- OPS checks - when all ground checks are finished leading into in-flight checks
- Lack of parts limits mission
- If FCF req., IAW T.O. 1-1-300, -6 Ins cards, Mx will NOT stop until FCF is accomplished
- FCF is part of an Mx action
-
Supply Status Starts
- Aircraft req.s mission essential part.
- Mx makes a valid demand ono supply and/or Depot
- Mx verifies part is essential
- Mx and supply verify no agency on base has part.
-
Supply Time Stops When?
- Mx receives part
- Whens upply receives part, even if Mx cannot accept it when available.
-
Minimum Essential Subsystems List (MESL)
- Lists minimum essential systems that MUST work for aircraft to perform assigned mission.
- Ref 21-103 Para 2.25
MAJCOMS lists minimum: Systems, subsystems, components
-
MESL
- Applies to code 3 and 4 discrepancies
- DOES NOT determine air worthiness or lfight safety
- Tech Data, Mx Crew and Air crew determine airworthiness
- DO NOT USE MESL to gauge "GO/NO GO" decisions
-
MESL
- Two List:
- Full Systems List (FSL)
-
All sys/subsys needed for FMC - Basic Systems List (BSL) Assigned missions & sys/subsys that must work to accomplish scheduled missions
- Qualifying Notes Describes components & conditions applicability of individual system
- Will aid in determining PMC and NMC status
-
Determining Aircraft Status
- FMC -- FSL = Full Systems List All systems, subsys and components with "x" in FSL col. work
- Sys/Component degraded but still capable of FMC
- PMC -- BSL = Basic Systems List
-
One or more sys, subsys or components are not working and have "X" in FSL column - Aircraft can do all BSL missions but not FMC
- NMC -- Aircraft cannot do any BSL missions
Red X Condition "Grounded"
|
|