163920: an E-6B Mercury database match

The saved aircraft database identifies this aircraft as Boeing E-6B Mercury. The type match does not independently verify its historical assignment or the purpose of this flight.

Recorded track: 6 saved positions over 2 minutes. Near Camden, Michigan; about 11.8 miles along the plotted segments.
Geographic plot of 6 saved aircraft positions in a short archived excerpt (Near Camden, Michigan). About 11.8 miles (10.3 nautical miles) along the plotted segments. Lines stop at gaps over 45 seconds, source changes and rejected positions. Archive timestamps do not establish exact message freshness. USGS topographic background shows roads, water and place names where available. It is a current reference map, not imagery from the flight date. Map data sources

Why this was our weekly pick

An E-6B Mercury database match stood out among the week's observations. This 707-derived aircraft type carries specialized communications equipment and serves as an airborne command post.

What the Mercury was built to do

Aircraft type background

Naval Air Systems Command describes the E-6B as an aircraft built to relay strategic communications and provide an airborne command post. Its predecessor, the E-6A, adapted Boeing's commercial 707 design for the Navy's TACAMO communications mission. The E-6B added staff positions and other equipment for the command-post role. NAVAIR dates the first E-6B acceptance to December 1997 and the start of its dual mission to October 1998. [1]

A 707 with trailing wire antennas

Aircraft type background

Boeing's historical account records 16 E-6 deliveries to the Navy between 1989 and 1992. They were assembled on the production line used for the E-3 Sentry, another aircraft based on the 707. Boeing describes two trailing wires used for very-low-frequency transmissions to support communications with ballistic-missile submarines. These are features of the aircraft type; the saved observation does not show whether those systems were in use. [2]

What the type match tells us

Interpretation

The saved aircraft database associates the observed address with registration 163920 and the E-6B Mercury type. The references explain that type's design and roles. They do not identify the purpose, crew or communications activity of the September 29 observation. The database association itself has not been independently verified against a dated airframe record. [2] [1]

What remains uncertain

  • The registration and type are aircraft-database associations, not independent historical identity verification.
  • Neither the track nor these type references establishes the flight purpose, occupants or use of onboard communications systems.
  • The archive has missing dates and a partial final date; this is a selection from available observations, not a complete record of regional traffic.

Research sources

  1. E-6B Mercury — Naval Air Systems Command. Aircraft type development and documented roles; no claim about the observed flight. Accessed .
  2. E-6 Mercury: Boeing historical product account — Boeing. E-6 production history and type equipment; no individual airframe or flight-purpose verification. Accessed .

Recorded observation

Observation
Observed to
Event typeUnusual aircraft
Recorded sourceMultilateration (MLAT)
Post date
Last revised
Aircraft
Aircraft typeBoeing E-6B Mercury
Type designatorE6
Tail number (registration)163920
ICAO addressAE0412

Measurements and times

Displayed measurements may be rounded.

Saved reading at .
Archived altitude; reference not retained11,875 ft
Transponder code0000
Record details

Public event ID: 8e10c0a0-9c4e-48db-985b-28d17bb82c07.

Record revision: 2.

Evidence version: ed372173e980cfb3b1c6768de089800ef97581990515939be8b1432d3965dbff.