The material defines a specific set of ASC codes that are considered valid. In that set, codes like ASC 00, ASC 01, and ASC 02 appear and are used in examples and references. There is no entry for ASC 03 in the material, so ASC 03 is not recognized within this documentation. When you’re studying or answering, rely only on the codes that are explicitly listed in the material; using a code not shown there isn’t supported by the material. The codes that do exist in the material (00, 01, 02) are valid for the contexts provided.

The main idea here is self-imposed disqualification. When a person requests to be barred from flying, the status used is Disqualified. Voluntary request. It explicitly shows that the disqualification was initiated by the individual, not caused by an agency action or by a lapse in certification. The other possibilities reflect different situations: Disqualified. FEB actions indicates an enforcement action by the authority, not a voluntary choice; DNIF/SUSPENDED/INITIAL covers other regulatory states such as not issuing a certificate, a suspension, or an initial status, which are not the same as a voluntary disqualification; Expired simply means the credential has expired, not that the person requested disqualification.

Amending an AO is the formal action used to fix minor administrative errors while keeping the same document in force and its original intent intact. When a typo, incorrect date, or other small wording issue is 견견, you correct it by amending the AO, and the updated version reflects those small corrections without altering the underlying requirements or scope. This is the best choice because it signals a precise, limited modification to the existing document. It isn’t about creating something new, extending how long the AO applies, or canceling it. A new AO would start a fresh document with potentially different content; extending changes the validity period; revoking cancels the AO entirely. Amending keeps the record coherent and traceable, with changes documented as a revision to the current AO.

Aerospace physiology training needs a dedicated, official record that clearly shows what training was completed, when, and by whom. AF Form 1522 is the Aerospace Physiology Training Record, and it’s designed exactly for that purpose. It records the trainee’s name, the specific training course or module, completion dates, test or evaluation results if applicable, and the instructor’s or examiner’s signature. This creates a single, verifiable dossier that flight crews and medical staff can reference to confirm readiness for flight duties and to satisfy regulatory or career-management requirements. Because this form is specifically designated for aerospace physiology training, it is the appropriate document for recording those activities. The other forms are used for different types of records or training data and do not serve as the official record for aerospace physiology training, so they don’t fit the purpose of documenting this training.

The main idea is keeping an official, auditable history of all published AOs and ASC changes within ARTEMIS. The record set is an electronic log that captures every published change in ARTEMIS in the order it happened, providing a traceable, version-controlled history. This makes it possible to verify which version is current, review what changed over time, and backtrack if needed for safety or compliance. A standard personal notebook isn’t controlled or auditable, so it wouldn’t serve as an official record. A maintenance log focuses on maintenance actions rather than changes to AOs and ASC within ARTEMIS. A training syllabus is about course content, not recording published changes in the system.