Type-rating preparation
Build a dependable mental model before course pace accelerates.
BOEING · B767-300
Build a connected understanding of source-to-bus and source-to-user reasoning across the major systems. Choose a preparation goal, browse the ATA map or collect the free readiness checklist.
12 PILOT BRIEFINGS
Build a dependable mental model before course pace accelerates.
Turn a manual chapter into a usable flight-deck explanation.
Study chapters in an order that exposes dependencies instead of hiding them.
Give structured answers that show understanding rather than rehearsed trivia.
Prioritise high-value recall, failure recognition and decision discipline.
Connect technical knowledge to margins, priorities and crew decisions.
Answer clearly under pressure without guessing beyond effectivity.
Build exact recall without separating numbers or actions from meaning.
Move from component failure to cockpit cue, retained function and operational consequence.
Prevent correct knowledge from being applied to the wrong variant or installation.
Replace fluent rereading and fact collecting with connected retrieval.
Use retrieval and spacing to strengthen a system model, not fragment it.
SYSTEM DIRECTORY
B767 ANSWER DESK
Clear answers for pilots planning a type rating, recurrent review, technical interview or command course.
Start with source-to-bus and source-to-user reasoning across the major systems. For each system, learn its purpose, sources, distribution, users, controls, indications, automatic logic and failure effects before memorising isolated details.
Begin with the cockpit indication philosophy, then the major energy paths. For the B767-300, early priorities include electrical distribution and standby capability, three hydraulic systems and RAT emergency path, flight controls, gear and braking users. This creates the dependencies needed for later failure and scenario study.
Use five passes: architecture, normal operation, controls and indications, automatic or protective logic, then failures and retained capability. Finish with mixed oral recall and current approved limitations or memory items.
Answer from purpose to consequence. State the system purpose, trace the normal path, identify what the crew controls and sees, explain automation, then describe what is lost, what remains and which effectivity boundary applies.
Use the sequence cue, automatic response, lost function, retained function and operational consequence. Keep system understanding separate from checklist actions, and use the current approved procedure for any operational response.
B767-300. Use 757/767 commonality to organise study, then verify every 767 control, user and effectivity detail.
Aircraft, engine, software and installed-option boundaries are treated as part of the answer rather than a footnote. Use 757/767 commonality to organise study, then verify every 767 control, user and effectivity detail.
The public library includes 12 pilot briefings and an aircraft readiness checklist. Active B767 members can also use the aircraft question bank, flashcards and interactive systems study guide.
No. FlightdeckQ is a training aid for building and testing understanding. Current approved aircraft, operator, regulator and training material remains authoritative for technical values, procedures and operational decisions.
No. FlightdeckQ is independent and is not affiliated with, authorised, approved, endorsed, sponsored or certified by Airbus, Boeing or any airline.
FLIGHTDECKQ B767
Move from public briefings into the B767-300 question bank, flashcards and member guide when you are ready to test the model.