B767-300 Type-rating preparation

Start with the B767-300 mental model

Build a dependable mental model before course pace accelerates on this aircraft means more than collecting facts. Build one connected explanation of source-to-bus and source-to-user reasoning across the major systems. Your notes should let you trace energy or information from its source, through distribution and control, to the flight-deck result.

Use the B767-300 boundary from the beginning. Use 757/767 commonality to organise study, then verify every 767 control, user and effectivity detail. This prevents a technically correct detail becoming a wrong answer when applied to another variant, engine, software standard or installed option.

A five-pass study sequence

1. 01

   Map the aircraft architecture and energy sources.

2. 02

   Learn normal controls, indications and automatic logic.

3. 03

   Connect systems through shared users and dependencies.

4. 04

   Study failure cues, retained capability and operational consequences.

5. 05

   Rehearse concise oral explanations and mixed scenarios.

Complete each pass from memory before reopening the source. Retrieval exposes missing links; rereading alone often hides them. Correct the model in your own words, then check it against current approved material.

B767-300 focus points

• 1. Electrical distribution and standby capability: explain the normal path, the flight-deck indication and what changes after a relevant source or distribution loss.
• 2. Three hydraulic systems and RAT emergency path: explain the normal path, the flight-deck indication and what changes after a relevant source or distribution loss.
• 3. Flight controls, gear and braking users: explain the normal path, the flight-deck indication and what changes after a relevant source or distribution loss.
• 4. Pneumatic, fuel and ETOPS interactions: explain the normal path, the flight-deck indication and what changes after a relevant source or distribution loss.
• 5. PW4000 and CF6 boundaries: explain the normal path, the flight-deck indication and what changes after a relevant source or distribution loss.

Do not try to recall all five areas at once. Study each system alone first, then mix two neighbouring systems and ask where they share power, data, air, hydraulic supply, indications or operational consequences.

Use this oral retrieval drill

“On the B767-300, describe the normal architecture, the crew controls and indications, the important automatic response, and the effect of losing one source or distribution path. State any variant or engine boundary before giving detail.”

Answer in two minutes. Draw while you speak. If you reach for a procedure, stop: this exercise tests system understanding, not memory of an operator checklist. Return to the current approved procedure for operational actions.

Common ways pilots waste study time

Copying long notes, memorising isolated components and treating question-bank scores as proof of understanding all create false fluency. A better correction is specific: identify the broken relationship, redraw that part of the system, explain it without notes and retest it after a delay.

Another common error is silent effectivity drift. For B767-300 study, write the applicable model, engine and configuration beside any fact that is not genuinely common. Use 757/767 commonality to organise study, then verify every 767 control, user and effectivity detail.

Readiness check

• I can state the purpose of each major system without notes.
• I can draw normal source-to-user paths.
• I can connect controls, indications, automation and protections.
• I can explain a failure as cue → automatic response → lost function → retained function → consequence.
• I can identify where B767-300 variant, engine, software or operator effectivity changes the answer.