3) Any review of required and specific TDIs are not clearly identified in the presail checklist. In conversations with CW3 Johnson, 605th, the presail checklist does capture the TDIs required in its layout. Additionally, in a 2/6/18, telecom with CW3 Willis, HMOD Cdr, notes that the presail checklist does capture some but not all TDIs (see File II B-4-4, tracker 16.) ISSUE: I do not believe the checklist serves as an effective communication tool or document for higher command for the validation of TDIs. RESPONSE: CW3 Willis states that TDI are present in the checklist, but not all. Additionally, the TDI’s are IAW AR 56-9 table 2-1. (See File B-4-9-1, item 7.) e. Presail checklist – reviewing for TDIs. Upon review of the order dated for 12 Dec 17 (See File II B-4-3-1) for the 163 TD, the presail checklist includes a check item for “Logbooks (Deck, Engine, TDI).” This check is noted in the checklist as “SAT” or “UNSAT” and an entered review date. No specifics as to which TDIs were reviewed. However, one could surmise that the TDI noted in the presail checklist applies to ALL the TDIs listed in AR 56-9 for “presail.” f. SOPs with requirements for licensing, training, and TDIs. (Per RFI question 2e) 1) Presail Inspections. In the 168 TD …show more content…
Deficiencies found in the documentation of completed TDIs in Log Books. I conducted a review of a small sample of TDIs, my findings show that my sampling found deficiencies in the records between the TDI listing found in the front of the logbook and the recording in the daily log pages. I have cases where the TDI roster has items noted as completed but do not cross-referenced to the day of recording in the daily pages. I cannot validate that the TDI was completed or not. If the presail checklist is only using the front pages of the logbook to validate that all required presailing TDIs are completed and not actually cross-referencing to the specific entry in the daily pages, we may have a serious weaknesses in controls. (REF: