ATC radar data blocks, as displayed in the FAA's Standard Terminal Automation Replacement System (STARS) and En Route Automation Modernization (ERAM) platforms, do include aircraft type information — but only when that information has been entered into the system. For instrument flight plan operations, aircraft type is filed directly and populates the data block automatically upon squawk correlation. For VFR flight following requests, however, no flight plan exists, and the controller must manually input the aircraft type, callsign, and other identifying information. During high-workload periods at a Class C or B terminal facility like Boston Approach, these manual entries are vulnerable to error, omission, or carry-over from a previous aircraft occupying the same data tag. The confusion described in the original incident — a Cessna being persistently labeled as a Malibu — is a textbook example of a corrupted or incorrectly assigned data block that simply was not corrected under traffic pressure.
The practical stakes of this misidentification extend well beyond an administrative inconvenience. ATC uses aircraft type to assign wake turbulence separation categories, sequence aircraft in the terminal environment, and anticipate performance characteristics during vectoring. A Cessna 150 cruising near 100 knots and a Piper PA-46 Malibu — which is, it should be noted, a high-performance piston single rather than a turboprop, with the turboprop variants being the Meridian, M500, and M600 — occupy vastly different performance envelopes. If a controller's mental model of an aircraft's speed and climb capability does not match reality, the sequencing decisions made on that aircraft's behalf may be suboptimal or, in compressed traffic situations, potentially unsafe. The pilot's repeated corrections were operationally appropriate and, under Part 91, entirely the correct course of action.
ADS-B Out, now mandatory for most controlled airspace operations under 14 CFR 91.225, has added a layer of aircraft identification data that was not available under older radar-only environments. An ADS-B Out transponder broadcasts ICAO aircraft address, flight identification, and in many implementations, aircraft category — data that populates directly into ground automation without controller manual entry. However, aircraft category codes in ADS-B (A1 through D7) are broad classifications rather than specific type designations, meaning they supplement but do not fully replace flight-plan-derived type data. For professional operators flying under IFR, the system generally works as designed; the vulnerability remains concentrated in VFR operations where no flight plan anchors the data block.
From an operational standpoint, working pilots and dispatchers in Part 91, 91K, and 135 environments should understand that data block accuracy is not guaranteed in the VFR flight following environment, and any miscommunication about aircraft identity should be resolved assertively with the controlling facility. Controllers are required to positively identify an aircraft before providing radar services, but the accuracy of ancillary data — particularly type — depends on workflow integrity that degrades under high traffic loads. Facilities like Boston Approach routinely manage complex, dense traffic mixing airline, business aviation, and general aviation targets, and manual data entry for VFR pop-ups is necessarily a lower priority task. Pilots operating high-performance light aircraft or jets in such environments should proactively confirm their type during initial contact and monitor whether ATC sequencing decisions appear consistent with their actual performance capability.