A Reddit poster's recollection of a startlingly close encounter between an America West 757-200 and a light twin resembling a Piper Seminole during a descent into Phoenix in the early 1990s has resurfaced as a reminder of how difficult it is to document near-miss incidents that predate the ubiquity of onboard recording, ADS-B tracking, and instant public reporting mechanisms. The poster, recalling the event as a child seated near the wing, describes a twin passing within an estimated 20-30 feet laterally at nearly the same altitude while in IMC during Arizona's monsoon season—conditions that would have afforded either crew essentially no time to see and avoid. No NTSB record, ASRS report, or news account has been located confirming the specific event, which is unsurprising given the era: NMAC (near mid-air collision) reporting in the early 1990s relied almost entirely on voluntary pilot reports to the FAA or NASA's Aviation Safety Reporting System, and unless a TCAS resolution advisory triggered a formal event log or a controller filed an operational error report, many close encounters simply went unrecorded outside informal crew debriefs.
For working pilots, the anecdote is a useful prompt to consider how far collision-avoidance technology and procedures have advanced since that period. TCAS II became mandatory on turbine aircraft with more than 30 seats in U.S. airspace in 1993, right around the timeframe described, meaning an America West 757 operating in the early 90s may or may not have had a fully mandated TCAS system depending on the exact date and equipage compliance deadline. A light twin like a Seminole, however, would almost certainly not have carried any transponder-based traffic alerting equipment at all in that era, relying solely on ATC separation and see-and-avoid principles—principles that are fundamentally compromised in IMC. This is precisely the scenario collision-avoidance mandates were built to address: mixed traffic environments near busy terminal airspace like Phoenix Sky Harbor, where air carrier jets on published arrivals and GA piston twins operating IFR or VFR can converge in weather that eliminates visual separation as a backstop.
The episode also underscores the enduring importance of terminal airspace design and controller workload management around major hubs. Phoenix in the early 1990s was a rapidly growing America West hub, and Sky Harbor's terminal airspace has since seen substantial redesign, including changes tied to NextGen PBN arrival and departure procedures, precisely to reduce the kind of vertical and lateral proximity conflicts described in the account. Modern arrival streams into major Class B airports are far more structured, with RNAV STARs, defined altitude windows, and much tighter integration between TRACON sequencing and traffic advisories than existed three decades ago.
For today's flight crews and dispatchers, the story is less about a specific unsolved incident and more about a broader lesson embedded in aviation safety culture: reported and recorded data only capture what pilots and controllers choose or are required to document, and near-miss history is inevitably incomplete for anything pre-dating ADS-B, expanded ASRS participation, and mandatory TCAS/TAWS logging. It reinforces why current safety programs emphasize robust, non-punitive reporting channels (ASAP, ASRS, and FOQA data-sharing) as a hedge against exactly this kind of institutional memory loss—ensuring that today's close calls, unlike this one, leave a traceable record for future investigators, safety analysts, and the traveling public.