AGANOMALY GRAPHLINK ANALYSIS← All dossiers sourced using AI
SOURCED USING AIuap

Mansfield Ohio Radar-Visual Military Case

Duplicate-source research lead: military aviation and radar documentation · 18 October 1973 · Mansfield, Ohio · United States

Also known as: Coyne radar case, Mansfield helicopter radar report, Coyne helicopter incident, Mansfield UFO case

WHAT THIS LABEL MEANS

This dossier is a research synthesis sourced using AI, not documentary evidence. Use the reference leads to check important claims.

This dossier concerns the event usually called the Coyne helicopter incident, reported near Mansfield, Ohio, on 18 October 1973. Its enduring reputation derives from the combination of a military helicopter crew’s visual account, reported aircraft-instrument anomalies, a claimed abrupt change in the helicopter’s altitude, and later references to air-traffic-control or radar information. Those elements should not be treated as four independent proofs of an extraordinary object. They are parts of one evolving aviation narrative, and the existence, timing, calibration, retention, and wording of any underlying radar or controller records remain central research questions. Recalled summaries commonly identify a U.S. Army Reserve helicopter crew, led by Captain Lawrence Coyne, returning through the Mansfield area at night when a bright light or object appeared on an apparent collision course. The crew reportedly altered course or prepared for an evasive response, after which the object passed or rose away. Accounts also associate the episode with a rapid uncommanded descent, unusual compass behavior, a green light, and an intense red or white illumination. Exact sequence, distances, altitude readings, duration, and whether all features were observed directly rather than reconstructed later vary across retellings. The case belongs as much to the history of postwar UFO investigation and popular aviation lore as to any question of anomalous aerospace evidence. A careful treatment separates contemporaneous reporting from later UFO-literature embellishment, distinguishes radar detection from radar interpretation, and considers ordinary possibilities including a bright astronomical body, aircraft lights, meteorological or visual-perception effects, instrument malfunction, stressed crew recollection, and errors introduced by repeated transmission. No paranormal or non-human explanation is established by the recalled material.

Words
2,384
Observations
12
Reference leads
5
Validation score
100/100

Chronology.

The reported date is 18 October 1973, during an evening or night helicopter flight in the Mansfield, Ohio, region. Recalled accounts place Captain Lawrence Coyne and other Army Reserve personnel aboard a helicopter travelling toward an intended destination, but particulars such as route, departure point, planned altitude, weather, and exact clock times require verification in flight documentation or contemporary reports.

During the encounter as later described, crew members noticed a bright light or structured-looking object ahead or above them and perceived it as rapidly closing. The reported response includes concern about a collision, an attempted manoeuvre or preparation to descend, changing cockpit indications, and the object’s apparent departure upward or away. The order of these details should not be assumed stable merely because later summaries present them as a smooth sequence.

In the immediate aftermath, the crew reportedly landed or otherwise made contact with military and aviation authorities. Some later treatments connect the event to air-traffic-control records and radar discussion, but a research file must establish which facility had relevant coverage, what was detected if anything, whether the information was contemporaneous, and whether it referred unambiguously to the helicopter or a second target.

From the mid-1970s onward, civilian UFO organizations, investigators, books, lectures, and encyclopedic compilations made the episode a prominent American military-aviation case. This transmission elevated a narrow set of memorable features, especially alleged radar corroboration, the green light, and a dramatic altitude change, while often leaving the documentary chain less visible than the narrative.

People, organisations, and setting.

The central reported witness is Captain Lawrence Coyne, usually described in retellings as the helicopter pilot and senior member of the Army Reserve crew. Other names frequently associated with the case include First Lieutenant Arrigo Jezzi, Sergeant John Healey, and Sergeant John Yanacsek, although each person’s exact duty, seat position, and role in every reported observation should be checked against primary flight and interview records.

The relevant institutional setting includes the United States Army Reserve, the helicopter unit or chain of command responsible for the aircraft and crew, and potentially Federal Aviation Administration air-traffic services. Civilian UFO research groups form a separate institutional layer because they gathered, interpreted, and publicized testimony; their accounts may preserve leads but cannot by themselves establish the content of military or FAA records.

Mansfield sits in north-central Ohio amid mixed urban, rural, and aviation environments. At night, horizon lights, aircraft traffic, changing sight lines, dark adaptation, cloud layers, and the limited visual references available from a helicopter cockpit can materially affect estimates of an object’s direction, distance, motion, and vertical position. The setting therefore matters to interpretation rather than serving only as a location label.

Reported visual, sensory, and behavioural phenomena.

Later accounts commonly describe a bright white, red, or green light associated with the reported object. Some versions portray a solid, cigar-like, domed, or disc-like form, whereas others make clear that form perception followed from an intense light source seen under difficult night conditions. Colour descriptions may reflect the object, atmospheric scattering, cockpit glazing, retinal afterimages, or the way witnesses and writers later selected salient details.

The crew reportedly experienced an imminent-collision impression and responded with heightened alertness, discussion among occupants, visual scanning, and an attempted avoidance action or readiness to descend. Such behaviour is evidence that the situation felt urgent to the witnesses, but it does not independently determine the object’s distance or identity. Perceived closing speed is especially vulnerable to ambiguous range cues at night.

Frequently repeated mechanical details include an apparent uncommanded loss of altitude, abnormal compass movement, and an unexpected increase in the helicopter’s vertical position after the object’s departure. These claims warrant separation into raw instrument readings, pilot perception, post-event reconstruction, and any maintenance inspection results. A dramatic statement that an object affected the aircraft is an interpretation unless a preserved technical record supports a causal mechanism.

The absence of reported collision damage, injury, or a publicly settled equipment finding is also significant. It does not disprove that the crew saw something unusual, but it limits what can be inferred about physical interaction. Investigators should record what the crew explicitly did not report as carefully as the striking features they did report.

Investigation and evidentiary history.

The principal research task is documentary reconstruction. Relevant materials may include flight plans, aircraft logbooks, crew statements, radio communications, maintenance forms, weather observations, unit correspondence, air-traffic-control tapes or transcripts, radar logs, and contemporaneous press coverage. The recalled lead specifically directs attention to the instrumental component, but it does not establish that any particular radar transcript survives or that it verified a nonconventional target.

Radar evidence, if found, must be evaluated at the level of the system rather than the label. Researchers should determine radar type, antenna sweep rate, altitude capability, coverage geometry, target identity, timing standard, weather-clutter conditions, primary versus secondary returns, controller annotations, and whether a purported return was recorded contemporaneously. A controller’s recollection of an unusual blip is not equivalent to a calibrated track demonstrating an object’s size, speed, or manoeuvre.

Interview evidence should be dated and compared across versions. Initial statements can reveal uncertainty that later retellings smooth over, while later interviews may add sincere but memory-shaped details. A useful case file would distinguish direct perception by each occupant, information learned from another crew member, statements attributed to controllers, and conclusions introduced by investigators or authors.

No recalled lead establishes a definitive government investigation with a published technical conclusion. The matter should therefore be described as a reported military aviation incident that attracted civilian UFO investigation, not as a solved official confirmation of an anomalous craft. The quality of the case depends on retrievable records and provenance, not on the number of later repetitions.

Disputes and alternative explanations.

The first dispute concerns the radar claim itself. UFO literature often treats the case as radar-visual, but this designation can conceal uncertainty about whether radar detected an independent target, merely tracked the helicopter, supplied contextual traffic information, or was recalled secondhand. Until original operational materials are authenticated, radar corroboration remains reported and disputed rather than established.

A second dispute concerns the reported altitude change. In a helicopter, apparent vertical motion can be affected by pilot control inputs, barometric setting, attention diverted toward an external threat, turbulence, updrafts or downdrafts, instrument reading error, and later conflation of events. An unexplained altitude excursion, if documented, would still not by itself identify an external object as its cause.

Astronomical, conventional-aircraft, and atmospheric explanations must be tested against precise time, direction, visibility, cloud cover, celestial positions, scheduled traffic, and the crew’s route. A bright planet or star can create a stationary-light illusion but may fit poorly with a rapid crossing account; another aircraft can fit lights and motion but may not fit all alleged manoeuvres. The appropriate conclusion is conditional comparison, not a reflexive single answer.

Skeptical and pro-UFO treatments may both overstate their preferred reading. Dismissal based only on the oddity of the story is inadequate, while a non-human explanation based only on witness credibility is equally inadequate. The lasting dispute is fundamentally evidentiary: which details are contemporaneous, independently corroborated, and accurately transmitted.

Later retellings, genre, and commercial influences.

The event was transmitted through witness interviews, UFO-investigator reports, newspaper and broadcast treatments, books, magazine articles, lectures, television programs, and online summaries. Each stage can compress uncertainty into a more memorable narrative. The phrase “radar-visual military case” is itself a useful search label but can become a promotional shorthand that implies stronger instrumentation than the surviving evidence may warrant.

The story’s genre appeal is unusually strong: trained military witnesses, a helicopter at night, an apparent near miss, cockpit instruments, a coloured light, and official communications all produce a cinematic account. These features help explain why the case has remained prominent in UFO anthologies. They also create incentives for publishers and speakers to foreground the most dramatic version, simplify disagreement, and treat internal consistency as if it were independent corroboration.

Commercial and organizational influences need not imply deliberate fabrication. Attention, book sales, media programming, organizational prestige, and the desire for exemplary “best cases” can reward selective emphasis without anyone consciously inventing an event. Researchers should map which detail enters the story at which publication stage and resist using a popular retelling to verify itself.

Cross-case connections and comparative motifs.

The case connects to other UAP reports involving military or professional aviators, apparent collision courses, night lights, claimed instrument effects, and asserted radar support. These are analytical motifs, not evidence that the same phenomenon, craft, agency, or cause was involved. Comparing cases is valuable only when data quality, aircraft type, environmental conditions, and source independence are assessed explicitly.

It also resembles a wider class of close-encounter narratives in which ambiguous lights trigger an urgent avoidance response and later become interpreted through technological language. Recurrent motifs include looming approach, colour change, sudden vertical departure, radio or instrument irregularity, and post-event official contact. Their recurrence may arise from common perceptual conditions and storytelling conventions as well as from any shared external stimulus.

A specific comparative question is how aviation incidents acquire instrumental authority in later circulation. Researchers can compare the Mansfield case with other alleged radar-visual reports by asking whether radar data were contemporaneous, independently preserved, capable of resolving altitude, and matched to the visual timeline. That approach avoids treating a repeated label as a demonstrated category.

Limits and responsible use.

This is an unverified recalled synthesis, not a documentary reconstruction. It does not demonstrate that a physical unknown object was present, that radar independently confirmed one, or that the helicopter underwent an externally caused altitude change. Names, technical details, and the sequence of events should be verified before use in historical, scientific, or public-facing claims.

The most responsible provisional formulation is that several Army Reserve personnel reportedly had a frightening nighttime aerial observation near Mansfield and that later sources associated the report with controller or radar information. This formulation preserves the testimony’s significance while avoiding claims beyond the accessible evidence. A future dossier should be revised against dated primary materials and should retain contradictions rather than silently harmonizing them.

Absence of accessible documentation is not proof that witnesses lied or that nothing occurred, but it constrains evidentiary confidence. Conversely, sincere testimony and possible aircraft records would not automatically establish paranormal, extraterrestrial, or otherwise extraordinary causation. The case is best retained as a high-interest, unresolved report with a substantial transmission history and a presently unverified instrumental component.

Chronology

18 October 1973, evening or night.

Reported helicopter encounter near Mansfield.

A U.S. Army Reserve helicopter crew reportedly observed a bright aerial light or object and experienced an urgent apparent near-collision situation near Mansfield, Ohio.

reported
18 October 1973, shortly after the observation.

Reported notifications and initial reporting.

Later accounts indicate that the crew communicated with military or aviation authorities, although the exact recipients, timing, and record trail require checking.

reported
October 1973, exact date unknown.

Potential operational-record creation.

Flight, maintenance, weather, air-traffic-control, radar, and unit records may have been created or retained, but no particular document is established in this recalled synthesis.

unknown
1970s, exact dates disputed.

Civilian UFO investigation and publication.

The case entered civilian UFO literature and began to be framed as a military radar-visual incident.

approximate
Later decades.

Expansion through popular retellings.

Books, lectures, television, and online accounts repeated and sometimes elaborated the narrative’s visual, altitude, and radar elements.

documented

People and roles

Captain Lawrence Coyne.

Reported helicopter pilot and central witness.

Later retellings generally identify Coyne as the senior pilot; precise service status and statement history require primary-source checking.

First Lieutenant Arrigo Jezzi.

Reported helicopter crew member and witness.

Frequently named in accounts of the incident, but duty position and individual observations should be verified.

Sergeant John Healey.

Reported helicopter crew member and witness.

Frequently named in later summaries; his direct observations should be separated from shared discussion aboard the aircraft.

Sergeant John Yanacsek.

Reported helicopter crew member and witness.

Frequently named in later summaries; spelling, duties, and statement chronology require checking.

United States Army Reserve.

Reported military institutional context.

The reported crew and helicopter were associated with the Army Reserve, subject to verification through unit records.

Federal Aviation Administration.

Potential air-traffic-control and radar-record institution.

Later narratives associate aviation-control information with the case, but the responsible facility and evidentiary content are unverified.

Civilian UFO research organizations.

Transmission and investigation network.

Such organizations helped preserve and publicize the case, but their later accounts are not substitutes for original operational records.

Connections to explore

Radar-visual claim.

Compare whether a visual report and an independently preserved radar track share a time base, location, and target identity rather than merely appearing in the same later story.

Suggested search: UAP radar visual cases original radar logs controller recordings provenance.

Military aviation witness credibility.

Compare how training, cockpit workload, night conditions, and later public status affect interpretation without treating military affiliation as automatic identification of the stimulus.

Suggested search: military pilot UAP reports night flight perception instrument workload.

Apparent collision course.

Compare looming and range-estimation problems in night aviation reports, including bright lights with uncertain distance and movement.

Suggested search: night aviation visual illusion apparent collision course bright light.

Instrument anomaly.

Compare claimed compass, radio, or altitude effects by separating raw recorded faults from witness recollection and proposed external causes.

Suggested search: UAP reports compass anomaly aircraft maintenance records.

Narrative amplification.

Compare early witness statements with later anthology and media accounts to trace when radar, colour, shape, and altitude details become fixed.

Suggested search: Coyne Mansfield case earliest interviews report publication chronology.

Unretrieved reference leads

LEADS, NOT CITATIONS These suggestions have not been retrieved or verified. They are starting points for source checking.
  1. Mansfield Ohio Radar-Visual Military Case.

    Unspecified recalled research lead. · Suggested research lead.

    This is the supplied discovery lead for locating original FAA, military, and controller documentation concerning the instrumental component.

    Suggested search: Coyne Mansfield helicopter FAA radar transcript October 1973.
  2. Contemporaneous U.S. Army Reserve flight and maintenance records concerning the Coyne helicopter incident.

    United States Army Reserve or successor custodian. · Potential primary operational records.

    These materials could clarify aircraft identity, crew roles, route, altitude, post-flight reporting, and any reported technical inspection.

    Suggested search: Lawrence Coyne helicopter 18 October 1973 Army Reserve flight log maintenance report.
  3. Contemporaneous FAA air-traffic-control communications and radar records for the Mansfield region.

    Federal Aviation Administration or archival custodian. · Potential primary aviation records.

    These materials are necessary to establish whether radar or controller information independently concerned a second target.

    Suggested search: FAA Mansfield Ohio 18 October 1973 Coyne radar controller records.
  4. Early civilian UFO-investigation reports on the Coyne helicopter incident.

    Unspecified civilian UFO investigators or organizations. · Suggested secondary research lead.

    Early reports may preserve interview dates, claim provenance, and contradictions that later summaries omit.

    Suggested search: Coyne helicopter incident earliest UFO investigation report 1973 1974.
  5. Contemporaneous Ohio newspaper and broadcast coverage of the Mansfield helicopter report.

    Regional news organizations. · Potential contemporaneous press records.

    Local coverage may help establish reporting dates, public statements, and the early form of the narrative.

    Suggested search: Mansfield Ohio newspaper Coyne helicopter UFO October 1973.