The question of pilot culpability when a Class D tower issues an instruction that results in a Class B airspace incursion sits at the intersection of two foundational regulatory principles that every instrument-rated and commercially certificated pilot must understand cold. Under 14 CFR 91.135, operating within Class B airspace requires an explicit ATC clearance — not merely an instruction from a controller, but a specific authorization from the facility that actually controls that airspace. A Class D tower does not control Class B airspace and therefore lacks the authority to issue a clearance into it. That authority belongs to the TRACON or combined Center/TRACON facility managing the Bravo. This means that even a well-intentioned "extend your downwind, I'll call your base" from a Delta tower controller cannot serve as a legal Class B clearance, regardless of whether the resulting ground track penetrates that airspace.
The pilot in command remains responsible under 14 CFR 91.3, which is unambiguous in placing final authority — and final accountability — with the PIC. Following an ATC instruction is a significant mitigating factor in any enforcement action, but it is not an absolute shield. The FAA's enforcement posture, as reflected in decades of NTSB case history and Legal Interpretations, consistently holds that pilots are expected to maintain situational awareness of their proximity to overlying or adjacent airspace. The "controller told me to" argument has been tested repeatedly, and while it can reduce the severity of a sanction or lead to the FAA exercising enforcement discretion, it does not eliminate the underlying violation. Courts and the NTSB have generally found that a reasonably prudent pilot should recognize when a controller's instruction is leading toward a boundary they are not authorized to cross.
The practical operational implication for working pilots — especially those flying in and out of Class D airports beneath or adjacent to Class B shelves in major terminal areas — is the obligation to anticipate and communicate before the conflict materializes. If a Delta tower's instruction is going to push the aircraft into Bravo, the correct response is a proactive radio call: something to the effect of "Extending downwind will put us in the Bravo, requesting clearance or an early turn." This puts the controller on notice, documents the situation on the recorded frequency, and gives the facility an opportunity to either coordinate a Bravo clearance or modify the instruction. Controllers operating Class D towers in busy terminal environments routinely deal with this geometry and generally appreciate the heads-up. Silence while flying into the shelf is the worst outcome for everyone.
From a broader trend perspective, airspace incursion enforcement has become a higher priority for the FAA as NextGen surveillance capabilities make deviations far easier to detect and reconstruct. Mode C transponder data, ADS-B Out tracks, and radar replay tools mean that a Bravo bust that might once have gone unnoticed now generates an automatic alert and a potential call from the FSDO. Filing an Aviation Safety Reporting System report immediately after any inadvertent incursion — particularly one where ATC instructions were a contributing factor — remains the most important protective step a pilot can take. The ASRS shield provides waiver of civil penalties for a single violation and signals good faith to the FAA. For Part 135 and Part 91K operators, an unreported Bravo incursion that surfaces later carries compounded consequences given certificate holder oversight and the duty to disclose deviations to the certificate-holding authority under some operations specifications. The regulatory answer may be nuanced, but the operational answer is straightforward: know the Bravo floor, watch the altimeter and moving map, and speak up before the problem becomes a violation.