A 1964 Piper PA-30 Twin Comanche, registration N741TJ, made a successful off-airport forced landing in a field southwest of Auburn Municipal Airport on April 18, 2026, after the crew lost power from both engines on approach to the Seattle-area airport. The pilot and passenger escaped without injury after the aircraft came to rest approximately 2.4 miles short of the runway. The flight had originated in Eureka, California earlier that day, a detail that immediately raises fuel planning as a primary investigative concern. The crew initially declared the emergency on the left engine and elected to continue toward Renton Municipal Airport, but a subsequent suggestion from Seattle Approach prompted the switch to the closer Auburn. Before the divert could be completed, the right engine also failed — reportedly around 2,200 feet altitude — leaving the crew with a single viable option: get it on the ground.
The dual engine failure signature in a light twin is a near-definitive indicator of a fuel system issue, and this incident appears consistent with that pattern. Both engines quitting sequentially rather than simultaneously can point to fuel exhaustion, fuel mismanagement, or cross-feed problems, and investigators will scrutinize fuel quantity records, fuel receipts, and the aircraft's fuel selector configuration. The absence of tip tanks on this particular PA-30 is operationally significant — tip tanks are a common and popular modification that substantially increases the Twin Comanche's usable fuel capacity, extending range well beyond the baseline 90-gallon system. An aircraft without tip tanks flying a long cross-country from Northern California to the Seattle area operates with considerably less margin for error or conservative fuel planning than an equivalently equipped aircraft would. The PA-30's Lycoming O-320 engines each produce approximately 160 horsepower, and the airframe is not equipped with automatic feathering — meaning both propellers observed in the feathered position in post-accident photographs required deliberate pilot action under severe workload conditions, which speaks to the crew's airmanship even as the outcome deteriorated.
The gear-down configuration for the off-airport landing will attract discussion among multi-engine instructors and check airmen. Deploying the landing gear on a power-off forced approach dramatically increases parasitic drag and shortens the glide, a trade-off that becomes acute when the touchdown zone is 2.4 miles short of the runway. In soft-field or unprepared surface landings, the conventional argument for gear-down is that it absorbs energy and prevents a sudden nose-over that can injure occupants; the argument for gear-up is that it extends glide range and reduces the risk of the gear snagging and causing a violent deceleration or rollover. This incident produced a survivable outcome with gear down in a dirt field, which aviation safety analysts will note but will not offer as universal guidance — the calculus changes considerably on pavement, ditches, or irregular terrain. What the outcome does reinforce is the growing body of anecdotal and investigated evidence favoring early selection of a suitable landing site over an extended glide toward a paved runway, a principle that Juan Brown of the Blancolirio Channel has identified as a recurring theme across recent forced landing accidents.
The ATC communication record, captured through an emerging real-time ATC replay and ADSB correlation application, provides a detailed timeline of the emergency progression and reflects how quickly the situation deteriorated after the initial mayday call. The crew's initial insistence on Renton — a longer airport with better infrastructure — followed by acquiescence to Auburn after controller prompting, and then the complete loss of options before Auburn could be reached, illustrates a compressed decision cycle that multi-engine crews are trained to manage but rarely exercise under actual emergency conditions. The controller's workload during the event, managing simultaneous IFR arrivals including an ILS sequence into Seattle-Tacoma's satellite airports, underscores the cognitive demand placed on the ATC system when emergency traffic enters the flow. For Part 91 and Part 135 operators flying light twins, the incident is a pointed reminder that single-engine service ceilings and divert range calculations must account for fuel state at the time of the failure, not at the time of departure.
The broader trend this incident joins is a cluster of light aircraft forced landings where fuel mismanagement — whether through exhaustion, selector error, or inadequate preflight planning on longer cross-country legs — remains a persistent and largely preventable causal factor. The PA-30 Twin Comanche is a high-performance, capable aircraft with a devoted ownership base, but its age and the complexity of its fuel system demand rigorous pilot currency and a methodical approach to fuel planning on any flight that approaches the practical range of the airframe. NTSB final findings will determine the precise mechanism, but the circumstances as reported align with a failure mode that training organizations and aircraft type clubs have addressed repeatedly over decades without eliminating from the accident record. Operators of any light twin — particularly those conducting longer cross-country flights without tip tank supplemental capacity — should treat this incident as a direct prompt to review their own fuel management SOPs.