The Phoenix Lights — 13 March 1997

On the night of 13 March 1997, observers across Arizona — and earlier in the evening across southern Nevada — reported two separate aerial phenomena that have been culturally bundled as the 'Phoenix Lights.' The first, between roughly 19:55 and 21:00 MST, was a slow, silent, V- or triangle-formation transit across the state, observed by thousands including then-Governor Fife Symington. The second, around 22:00 MST, was a row of stationary lights over the Estrella Mountain range south-southwest of Phoenix, later confirmed as a Maryland Air National Guard parachute-flare exercise during Operation Snowbird training. The Council files both events under this case number and assigns each its own verdict: Inconclusive for the earlier triangular formation; Debunked for the 22:00 flare drop.

The cultural memory of “the Phoenix Lights” treats 13 March 1997 as a single event. The contemporaneous record does not. What occurred over Arizona that night was two distinct phenomena, separated by roughly an hour, by tens of miles of ground track, and by the kind of explanation each one admits. Their conflation is the central failure mode of nearly three decades of public discussion. The Council’s archive holds both events under this case number and assigns each its own verdict — because the discipline of separating them is the only way the public record gets the case right.

This file consolidates the full Council reconstruction of the 13 March 1997 events. A parallel file at Case #00013 — Phoenix Lights, Triangular formation covers the earlier transit in isolation; the present file is the primary case and treats both events together. The Council’s recommended posture for any reader engaging with the popular literature on the case is to first establish which event is being discussed before evaluating any claim about it.

The two-events framework

The shorthand “Phoenix Lights” refers, in practice, to two phenomena that overlapped on the night of 13 March 1997 and have been merged in public memory ever since.

Event A — the triangular transit (~19:55 to ~21:00 MST). A slow, silent, V- or triangle-shaped formation of lights crossing southern Nevada, northern Arizona, the Phoenix metropolitan area, and continuing toward Tucson. Reports describe an object — or an aircraft formation — appearing to span a substantial angular size of sky, moving at low apparent altitude, and producing no audible engine signature consistent with conventional powered flight. This is the event Symington later acknowledged personally observing. It is the analytically distinctive part of the case and the part for which no fully satisfactory mundane explanation has been published.

Event B — the flare drop over the Estrella Mountains (~22:00 MST). A horizontal row of stationary lights, captured on multiple home video cameras, appearing and disappearing in sequence over the Estrella Mountain range south-southwest of Phoenix. This is the event most often shown in television documentaries because the footage is dramatic. It is also the event that has a documented, on-the-record official explanation: a high-altitude LUU-2B/B parachute-flare exercise by A-10 Warthogs of the 104th Fighter Squadron, Maryland Air National Guard, conducted from Luke Air Force Base as part of Operation Snowbird training.

These are not minor variants of one event. They occurred in different parts of Arizona’s airspace, were observed by different witnesses (with some overlap), have different physical signatures on the recorded media, and admit different verdicts. The Council’s position is that any analysis that treats the two as a single phenomenon is, on that ground alone, defective.

Event A — the triangular transit

Timeline

The earliest reports of Event A originate in southern Nevada near Henderson at approximately 19:55 MST on 13 March 1997, where observers described a V-shaped formation of large lights moving slowly southeast at low apparent altitude. Within roughly twenty minutes the same — or a closely matching — formation was reported over Paulden, Arizona. Reports cascaded south through Prescott, the Verde Valley, and into the Phoenix metro between approximately 20:15 and 20:45 MST. The trailing edge of the transit continued toward Tucson, where observations near 20:45 to 21:00 MST describe the formation passing overhead before disappearing to the south.

Witness consistency on the formation’s geometry is unusually high for a mass sighting of this scale. Observers separated by hundreds of miles independently described a wedge or boomerang pattern of five to seven distinct lights, slow forward motion, no audible engine signature, and — in many accounts — the appearance of an opaque structure occluding stars between the lights.

Named witnesses

Council practice requires distinguishing the principal first-person witnesses by category. For Event A, four are central.

Tim Ley, a Phoenix-area resident, observed the formation from his suburban yard with his wife Bobbi, son Hal, and grandson Damian. Ley’s account is one of the most-cited civilian observations of Event A. He has described the formation as initially appearing as five distinct lights in an arc several miles away, then growing in apparent size as the formation approached, then passing directly overhead at what he assessed as low altitude with an object he perceived as a single carbon-black structure spanning the lights. The Ley family produced still photographs of the formation that are part of the public record.

Mike Krzyston, a Phoenix resident, captured one of the most-circulated video records of Event A from a balcony in the city. The Krzyston tape shows distinct lights in formation, slow motion across the field of view, and — critically for analysts — sufficient duration and steady framing to permit subsequent angular-velocity analysis.

Trig Johnston, a commercial pilot, observed the formation while in the air. His in-flight observation is among the most evidentially weighted civilian-side accounts because of the platform: a trained airman observing aerial traffic from an aircraft has a calibration on altitude, distance, and aircraft type that ground-based observers do not. Johnston’s contemporaneous account has been consistent across decades of subsequent interviews.

Fife Symington, then-Governor of Arizona, observed the formation from his Phoenix residence. His response in the months following the event — including the staged 26 June 1997 press conference at which his chief of staff was brought out in a gorilla suit ostensibly as the “captured alien” — became one of the case’s most-criticised public moments. In a 2007 CNN op-ed and subsequent televised interviews, Symington publicly reversed his earlier dismissal and stated that he had personally seen “a massive, delta-shaped craft silently navigating over Squaw Peak.” He characterised the 1997 press conference as a deliberate exercise in calming public concern at a moment when the Governor’s office was receiving thousands of calls. Symington has maintained the 2007 account in subsequent interviews and in his public correspondence.

Additional named witnesses in the public record include Frances Barwood, then a member of the Phoenix City Council, who became a principal public voice pressing for an official investigation in the months following the event. Barwood’s persistence — including her later 1998 gubernatorial campaign in which the lights were a stated issue — kept Event A on the political agenda even as institutional Arizona moved past it.

Photographic and video record

The Event A record includes at least a half-dozen distinct video captures and several still-photograph sets. The Krzyston tape, the Ley still photographs, and several less-widely-circulated home-video sources together constitute the principal media archive. Two analytical features of the record matter.

First, angular size and apparent velocity vary across sources in ways that constrain — but do not uniquely determine — the underlying object’s distance and altitude. Analysts working from the videos have produced both low-altitude/large-object and high-altitude/distributed-formation reconstructions; both can be made consistent with subsets of the recorded media.

Second, the absence of clear audio in the videos is one of the case’s more durable analytical features. Modern jet aircraft at the altitudes that would explain the rapid ground-track transit produce engine signatures that should be audible at ground level under the meteorological conditions of that evening. The absence of such signatures in the videos has been raised by analysts on multiple sides of the case.

Event B — the Estrella flare drop

Timeline

At approximately 22:00 MST, roughly an hour after Event A had transited the Phoenix metro and continued toward Tucson, a new set of observations began from the south side of Phoenix. These observations described a horizontal row of stationary lights — initially perceived as suspended objects — appearing in sequence in the southwestern sky and then, after a period of apparent hover, disappearing one by one in the same sequence in which they had appeared.

Multiple Phoenix-area witnesses captured this event on home video. The footage shows the row of lights, the apparent stationary phase, and the sequential extinguishment. Because this footage is dramatic, easily shot from a residential balcony, and replayed extensively in television treatments, Event B has become the visual shorthand for “the Phoenix Lights” in popular memory — even though it is the part of the case for which a documented official explanation exists.

The Operation Snowbird explanation

In June 1997, Lt. Col. Ed Jones of the 104th Fighter Squadron, Maryland Air National Guard, confirmed that A-10 Warthogs of the squadron — deployed to Luke AFB as part of Operation Snowbird, the annual winter training rotation — had conducted a high-altitude LUU-2B/B parachute-flare drop over the Barry M. Goldwater Range on the night of 13 March 1997. The drop was a standard training exercise. The flares were released at altitude and fell behind the Estrella Mountain range from the perspective of Phoenix-area observers, producing precisely the sequential appearance-and-disappearance pattern the home videos record.

The Maryland ANG confirmation is unusually specific: it identifies the unit, the operation, the type of munition, and the geography of the drop. It is corroborated by the flight times and ordnance records of the squadron and by Luke AFB’s contemporaneous range-use logs. The Council assesses this confirmation as directly responsive to the Event B record and as a complete explanation of the 22:00 observations.

The geometry of the explanation is also straightforward. Observers facing the Estrella Mountains from the south side of Phoenix would have seen flares illuminated above the ridgeline as bright stationary points, then watched each one disappear from view as it descended behind the ridge from the observer’s line of sight. The disappearance is sequential because the flares were released sequentially. The effect of stationary hover is a function of the flares’ descent rate against their high apparent altitude. Nothing in the home-video record of Event B is inconsistent with this geometry.

Official response

The official response to the 13 March 1997 events has unfolded in three phases.

Phase 1 — initial denial and confusion (March–May 1997). In the days immediately following the event, Luke Air Force Base issued public statements denying knowledge of any military activity that could account for either Event A or Event B. The denials were broad and did not differentiate between the two phenomena. They were also, with respect to Event B, subsequently superseded by the Maryland ANG’s June confirmation. With respect to Event A, the denials remain the operative official position to the present day.

Phase 2 — the Maryland ANG confirmation (June 1997). The 104th Fighter Squadron’s confirmation that it had dropped flares over the Goldwater Range on 13 March 1997 was issued in response to sustained press inquiry — particularly from the Phoenix New Times — and resolved Event B as a matter of formal record. The confirmation did not address Event A, and the Maryland ANG has not made a claim about the earlier transit.

Phase 3 — the Symington reversal and subsequent inertia (2007–present). Symington’s 2007 public statement that he had personally observed an unidentified craft on the night in question reopened public discussion of Event A but did not produce any new official investigation. Neither USAF, nor the FAA, nor — in the years since its 2022 establishment — the All-domain Anomaly Resolution Office (AARO) has formally re-investigated the 1997 events. The AARO Historical Record Report Volume I, released in March 2024, does not address the case in detail. The result is that Event A retains the same official posture today as it had in mid-1997: no positive identification, no formal investigation, and no claim of jurisdiction by the responsible aviation or defence authorities.

The political record around the case has also been documented in part. Frances Barwood’s repeated requests in 1997 for the Arizona Governor’s office to support a formal investigation are part of the Phoenix City Council record. Symington’s 1997 press conference, his 2007 reversal, and the gap between them are the most-cited illustration in the popular literature of how an official response to a mass observation can shape the public record long after the underlying event has receded.

Mundane explanations considered

A defensible Council verdict on either event requires considering every plausible non-anomalous explanation on its merits. The Council considers five — applied separately to Event A and Event B because the two events admit different explanations.

1. The flare-drop explanation (decisive for Event B; inapplicable to Event A)

The Maryland ANG flare-drop explanation accounts for the 22:00 Event B observations completely. It accounts for the row of lights, the apparent stationary phase, the sequential disappearance, the observed bearing from the Phoenix metro toward the Estrella Mountain range, and the timing within the squadron’s range-use log. The Council credits it without reservation as the correct explanation for Event B.

The same flare-drop explanation is not applicable to Event A. Event A occurred between approximately 19:55 and 21:00 MST — roughly an hour before the flare drop — and traversed hundreds of miles of ground track from southern Nevada through the Phoenix metro toward Tucson. A stationary flare exercise over a single range south of Phoenix cannot account for an aerial transit that began in Henderson and continued past Phoenix toward Tucson. The proposal that Event A was “also flares” is an instance of the conflation failure mode the Council’s two-events framework exists to prevent.

2. Conventional aircraft formation at altitude (the principal hypothesis for Event A)

The most analytically substantive non-anomalous explanation for Event A is that observers across the state independently observed a formation of conventional aircraft at high altitude, with apparent angular size and apparent low altitude being functions of misjudged distance. The hypothesis has been steel-manned by several analysts — most prominently the skeptical researcher Tim Printy, whose published work on the case is the most thorough non-anomalous treatment in the public literature.

Printy and other analysts have argued for two principal candidate formations: a flight of A-10 Warthogs transiting south to or from Operation Snowbird activity at Luke AFB; and a flight of high-altitude B-2 or B-52 bombers in formation, with the apparent low altitude being a perceptual error driven by the relative darkness of the night sky and the absence of nearby reference structures for ground observers.

The Council credits the following from this analysis. First, formation flying at altitude can produce the apparent angular geometry of a single large object under specific viewing conditions, particularly when observers have no fixed reference for distance. Second, the formation hypothesis is internally consistent with the broad ground track of Event A reports, given the southerly direction of routine military air traffic in the region. Third, at least one ground observer — Mitch Stanley, observing through a 10-inch Dobsonian telescope — has stated that the lights resolved into discrete aircraft at magnification, an observation which, if accepted, is a substantial weakening of the “single structured object” reading.

The Council also notes the limits of the formation hypothesis. It does not cleanly account for the absence of audible engine signatures consistent with the altitudes required to make the ground-track timing work. It does not explain why no Air Defense Identification Zone or FAA radar track has been released that would corroborate the proposed flight. And it does not address the consistency of low-altitude perceptions across observers separated by hundreds of miles. These are not decisive objections — but they are why the Council does not credit the formation hypothesis as a complete explanation.

3. Misidentification of high-altitude bombers (a sub-variant of #2)

The specific high-altitude-bomber sub-variant advanced by Tim Printy and others deserves separate consideration because it engages the angular-size objection directly. Printy’s argument is that observers, lacking any altitude reference, defaulted to assuming the lights were at a familiar altitude — the altitude of an airliner on approach to Sky Harbor — and that this perceptual default is what produced the consistent low-altitude reports. At the genuine altitude of the proposed bomber formation, the formation would be inaudible from the ground and the apparent ground-track timing would be within plausible bounds.

This is a serious argument. The Council engages it on its merits and credits the perceptual-default mechanism as a real cognitive feature of mass-observation events. The Council does not, however, treat the hypothesis as decisively confirmed, for the reasons given above and because no released flight record has been produced that confirms a bomber formation on the relevant ground track at the relevant time.

4. A single very-high-altitude transit (e.g., a high-altitude balloon array or test vehicle)

A small number of analysts have proposed that Event A might have been a high-altitude balloon array, a tethered test vehicle, or a similar slow-moving aerial structure. The Council notes the hypothesis without endorsing it: the ground-track timing and witness consistency on motion across hundreds of miles do not match the behaviour of a typical balloon, and no test programme of the proposed type has been declassified for that period and region.

5. Mass hysteria or post-hoc convergence on a single narrative

A fifth class of mundane explanation holds that the consistency of witness accounts is itself a product of the media coverage that followed the event, and that the underlying observations were heterogeneous before the press treatment normalised them. The Council credits the partial validity of this mechanism — media coverage demonstrably shapes how witnesses recall and re-tell observations — but notes that the most-cited contemporaneous reports, including the Ley family’s account and the Krzyston video, predate the saturating press treatment of late March 1997. Post-hoc convergence cannot account for the original reports filed in the first hours after the event.

Open questions

After more than a quarter-century, the questions on the Council’s open list for Event A are narrower than they were in 1997 but remain material.

• The FAA’s radar coverage of the proposed ground-track region on the evening of 13 March 1997, if it captured any of the Event A formation, has not been released in a form that would allow independent reconstruction.
• No USAF flight record has been declassified that confirms (or rules out) a bomber or fighter formation on the Event A ground track at the relevant time.
• The chain of custody of the principal video sources — Krzyston, Ley, and others — has been documented unevenly; original tapes versus copies have not always been clearly distinguished in published analyses.
• Symington’s 2007 reversal opened a door that no subsequent governor or federal authority has walked through; the absence of a formal Arizona-state-level inquiry into Event A remains a public-record gap.
• AARO has not formally addressed the case in its public reporting through the FY2025 cycle.

For Event B, the Council considers the documentary questions resolved. The Maryland ANG confirmation, the Operation Snowbird records, and the Goldwater Range geometry together close the question of what the 22:00 lights were.

The Council’s verdict

This case carries two verdicts — because it is, in fact, two cases that have been culturally bundled into one. The Council files them together because the cultural memory of “the Phoenix Lights” treats them as a unit and any responsible reference page must address that unit. The verdicts themselves are separate.

Event A — the triangular transit (~19:55–21:00 MST): Inconclusive.

The transit across Arizona on the evening of 13 March 1997 is not, on present evidence, sufficient to support a “Confirmed” verdict. Mitch Stanley’s telescopic observation, the steel-manned formation-of-aircraft hypothesis advanced by Tim Printy and others, and the perceptual-default mechanism for misjudged altitude together constitute a substantive non-anomalous account that the Council credits — even though that account does not, in the Council’s reading, decisively close the question. At the same time, the case is not sufficient for a “Debunked” verdict either. The absence of an audible engine signature, the consistency of witness accounts across hundreds of miles of ground track, the lack of any released military or FAA flight record corroborating the proposed formation, and Symington’s 2007 first-person confirmation are not consistent with a fully resolved skeptical explanation. The case sits where it has sat since 1997 — in the genuinely unresolved middle, where the Council’s discipline holds it.

Event B — the 22:00 row of lights over the Estrella Mountains: Debunked.

The Maryland Air National Guard’s June 1997 confirmation that the 104th Fighter Squadron conducted a high-altitude LUU-2B/B parachute-flare exercise over the Goldwater Range on the night in question is a complete, documented, and unit-specific explanation of the 22:00 observations. The geometry of the explanation matches the home-video record. The Council credits the explanation as decisive and assigns Event B a verdict of Debunked.

That the same case file holds an “Inconclusive” verdict and a “Debunked” verdict is not a failure of analysis. It is the analysis. The two events occurred on the same night and have been conflated for nearly thirty years; separating them — and assigning each its own verdict on its own evidence — is the work the case has been waiting for. For readers approaching the case for the first time, the practical recommendation is this: when a documentary or article refers to “the Phoenix Lights,” ask which event is being discussed before evaluating any claim about it. Most of the public record’s confusion about this case is downstream of that single question being left unanswered.

A future release of FAA radar tapes, declassified USAF flight records for the evening of 13 March 1997, or a formal AARO Historical Record Report treatment of the case would meaningfully change the Event A assessment. Absent such releases — and the Phoenix Lights record is closely paralleled in this respect by the Rendlesham Forest case, where contemporaneous documentation outpaced subsequent official acknowledgement — Event A remains what it has been for a quarter-century: the most-reported, least-explained mass observation in the modern American UAP record.

For the broader Phoenix-area observation context that surrounds this case, see the Council’s Phoenix, AZ sightings reference. For an in-depth treatment of Event A in isolation, see Case #00013. For the modern Navy parallel in which contemporaneous instrumented record outpaces official acknowledgement, see Case #00041. The relevant glossary entries for terminology used in this file are UAP, AARO, NUFORC, and MUFON.

Sources

1. Phoenix New Times, contemporaneous reporting on the 13 March 1997 events, including Tony Ortega and other staff reporting through 1997–1998.
2. Maryland Air National Guard, 104th Fighter Squadron — Operation Snowbird flare-drop confirmation, public statement via Luke AFB (June 1997).
3. Fife Symington, “I saw a UFO in the Arizona sky,” CNN op-ed and accompanying televised interview (9 November 2007).
4. Tim Printy, “What I Have Learned About the Phoenix Lights,” SUNlite / astronomyufo.com — independent skeptical analysis.
5. The Arizona Republic, contemporaneous reporting, March–April 1997.
6. All-domain Anomaly Resolution Office (DoD), Historical Record Report Volume I, March 2024.
7. Mutual UFO Network, Phoenix Lights consolidated case file.
8. City of Phoenix Council records — Frances Barwood statements and correspondence, 1997.