Career Feats
Beechjet 400 — FMS fixes unavailable (preflight)
While the captain managed other preflight duties, the FMS would not accept the filed GPS fixes. London entered user waypoints via latitude/longitude directly into the CDU, verified each coordinate against charts, and reconstructed the route. He confirmed the routing with ATC and ensured proper leg sequencing and discontinuity resolution. Result: ATC-cleared flight plan loaded and the flight departed as scheduled.
Challenger 850 — HYD 1 LO PRESS in flight
The crew received a HYD 1 LO PRESS caution. London executed the QRH, confirmed indications, and used the boost/AC motor pump to stabilize System 1 pressure at ~1800 PSI while monitoring trends. When pressure decayed below that threshold, he recommended and executed a precautionary diversion to KLEX in accordance with procedure. Result: Safe landing, passengers transferred to a recovery aircraft, and the airplane remained AOG for several days until MX completed corrective action.
Challenger 850 — stuck mic / lost comms after departure
Shortly after takeoff, the crew noticed frequency blocking and loss of receive audio. London rapidly diagnosed an intermittent captain-side PTT (already MEL-deferred) that was being triggered by light turbulence/control movement. He isolated the captain transmit path, shifted operations to COM 2 to restore two-way comms, and implemented a mitigation by parking 123.45 on COM 2 so any hot-mic event would be sequestered there while London maintained ATC on COM 1. Result: Communications restored without diversion; lesson captured in debrief/SOP notes.
Challenger 850 — FMS "Aircraft Not On Ground" lockout (maintenance pickup at KMCN)
During setup, both FMS units displayed "Aircraft Not On Ground," preventing route edits. Line maintenance attempted an FMS swap but aborted when part numbers didn't align, precluding R&R. At the captain's request, London prepared a Victor airway / ILS raw-data contingency. He then methodically troubleshot the FMS: built the entire filed route in the Secondary Flight Plan, executed it, and then activated the alternate plan, which cleared the lockout and restored full GNSS/FMS functionality. Result: Full GPS navigation regained and the leg was completed normally, with the raw-data plan retained as a backup.
Challenger 850 — Preflight static port obstruction (copilot side)
During an extensive exterior inspection, London spotted white particulate matter occluding the copilot-side static port. He photographed the finding, briefed the PIC, and paused dispatch. Under supervision and per procedure, the obstruction was carefully cleared, then the crew verified both static ports were unobstructed and performed appropriate pitot-static/air-data checks (altimeter/baro set, instrument responsiveness, no P/S flags). Result: A likely air-data anomaly (altitude/airspeed/VSI errors) was prevented before engine start—reinforcing the value of meticulous preflight inspections.
Nantucket night operations — route stop & WATRS solution (ACK)
After landing in Nantucket, MA (ACK), London picked up the next-leg clearance and immediately queried a "stop" advisory—confirming it was a route stop: the filed Q-route was unavailable and no alternates were initially accepted. This was a shuttle operation under enhanced security procedures, and with TSA screeners nearing duty-out and no hotel availability, the flight risked cancellation. The chief pilot's office proposed a security role reassignment to keep the operation viable—designating London as Ground Security Coordinator (GSC) (U.S. citizenship requirement met) while the team worked the routing. After multiple calls and initial denials, an assistant chief pilot suggested trying a Y-route. London questioned the proposal, flagging potential oceanic/WATRS exposure and the aircraft's lack of HF capability, then requested authoritative guidance. With documentation confirming the FAA Yankee (Y) routes within WATRS were an appropriate high-altitude RNAV option for the profile, while flying under domestic rules, London coordinated with his captain, rebuilt the flight plan, and obtained the amended clearance. Result: Departed approximately six hours behind schedule—but 30 minutes before duty-out would have scrubbed the mission—maintaining compliance, security oversight, and operational continuity.
London's Operating Style
London combines QRH discipline, CRM importance, and MEL awareness with deep secondary-plan mastery, keeps communications cleanly when systems misbehave, flies raw data with confidence, and leads crisp CRM that keeps passengers safe while protecting dispatch reliability and completing the mission.