Event

Coyne Helicopter UFO Incident

In 1973, an Army Reserve helicopter crew over Ohio reported a close UAP encounter that appeared to affect the aircraft's climb.

0
Mentions (30d)
0
Active Signals
1
Feed Sources
5
Co-mentions
Coverage evidence mix
Opinion2
Probed Analysis

The Coyne Helicopter UFO Incident took place on October 18, 1973, during an Army Reserve helicopter flight over north-central Ohio. The crew, led by Captain Lawrence Coyne and including co-pilot Arrigo Jezzi and other personnel, reported a close encounter with a bright object while flying a UH-1 helicopter. The case is often associated with Mansfield, Ohio, and remains one of the better known aviation reports from the 1973 U.S. UFO wave.

According to the crew's later accounts, the object first appeared as a red light that seemed to be on a collision course. Coyne reportedly began a descent to avoid it. The crew then described the light changing appearance, passing near or over the helicopter, bathing the cockpit in green light, and coinciding with an unexpected climb. Those details are the extraordinary center of the case: witnesses claimed the aircraft behaved in a way they did not command or expect.

The event entered UAP history because it involved a trained military crew, an aircraft in flight, and a report of possible physical interaction. Aviation cases carry extra weight when the observers have cockpit experience and when the event includes aircraft performance rather than only lights in the sky. The Coyne case is also notable because it was discussed by UFO researchers, appeared in later case compilations, and became part of the argument that some UAP reports involve close proximity to military aircraft rather than distant ambiguous lights.

The documentation available in public is still mostly witness-centered. There is no public instrument package that independently proves the object's path, distance, speed, or effect on the helicopter. The crew accounts are consistent enough to keep the case alive, but they are not the same as a preserved flight-data record. Conventional possibilities include misidentified aircraft, astronomical or atmospheric effects, stress during an apparent collision threat, or errors in reconstructing altitude and control inputs after a startling event. None of those explanations cleanly resolves every reported detail; they frame the uncertainty.

The named crew is the heart of the record. If Captain Coyne's account is accurate, the incident would be a close-range aviation safety event involving an unidentified object and an unexplained climb. If the account is distorted by memory, lighting, or cockpit confusion, the case shows how a high-stress flight event can become a durable UAP narrative. Both readings matter to aviation-centered UAP history.

Internal links are still thin for this case, but J. Patrick Coyne and broader official-study context such as AARO help place it among older military witness cases now revisited during modern disclosure debates.

Probed read: The strongest feature is the quality of the witness category: a military helicopter crew reporting a close-range event. The weakest feature is the lack of publicly available contemporaneous instrument data that could separate perceived aircraft behavior from a measured external effect.

What would move the assessment: Original Army reports, flight logs, radio traffic, maintenance checks, and signed crew statements from immediately after the flight would materially improve confidence. A verified conventional aircraft track or other contemporaneous explanation matching the geometry would weaken the anomalous reading.

Filters
Time Range
independentApr 22

Case Files MARATHON | Somewhere in the Skies

independentApr 22

Case Files MARATHON | Somewhere in the Skies ๐Ÿ“ฑ

Mention Velocity
30d agoToday
Source Mix
2items
Somewhere in the Skies2
Related Signals
0