This forum inquiry, though modest in scope, touches on a subject of genuine interest to aviation professionals and enthusiasts alike: the traceability of historical flight operations and the lifecycle of specific airframes. The original poster is seeking the tail number of a United Express regional jet—likely operated by a carrier such as Air Wisconsin, Mesa, SkyWest, or Trans States under the United Express banner—that flew from Moline, Illinois (MLI) to Denver (DEN) on August 13, 2001, just weeks before the September 11 attacks reshaped commercial aviation. The request highlights a common challenge: pre-9/11 flight data, particularly at the granular level of individual tail number assignments to specific flight numbers on specific dates, is not comprehensively archived in publicly accessible databases the way post-2010s data is through platforms like FlightAware, Flightradar24, or ADS-B Exchange.
For working pilots and aviation operators, this scenario underscores an important operational and historical reality: tail number assignments to scheduled flights have never been fixed or guaranteed, and record-keeping practices have evolved significantly over the past two decades. Prior to the widespread adoption of ADS-B (Automatic Dependent Surveillance-Broadcast) technology, which the FAA mandated for most controlled airspace operations by January 2020, flight tracking relied heavily on ACARS (Aircraft Communications Addressing and Reporting System) data, radar returns, and airline-internal dispatch records—none of which were systematically published for public retrospective search. Regional carriers operating CRJ-200s in the early 2000s under contract to major airlines like United would have maintained aircraft rotation schedules internally, but these are not typically retained or released for public research decades later. This matters to pilots and dispatchers because it illustrates how much aviation's data infrastructure has matured; today's operators benefit from real-time, granular tracking that simply didn't exist in a publicly queryable form 25 years ago.
The broader significance for the aviation community lies in the growing interest in aircraft "life history" tracking—a niche but active area of enthusiasm among planespotters, aviation historians, and even airline maintenance planners who use tools like the FAA's registry database, Planespotters.net, and JetPhotos to trace an airframe's registration changes, operator history, and eventual fate (whether still in service, parted out, or stored). CRJ-200s from the early 2000s are now well into their third decade of service, and many have transitioned from mainline regional contracts to cargo conversion, charter operations, or retirement, reflecting the broader fleet-renewal trends affecting the 50-seat regional jet segment. This segment has been steadily shrinking industry-wide due to scope clause restrictions, pilot shortages, and the economics of smaller aircraft, making questions like this one a small window into a much larger story about regional aviation's evolving fleet composition.
For corporate and Part 135 operators, the anecdote also serves as a reminder of the value of robust internal record-keeping. While this particular request concerns a legacy airline's historical operations, business aviation operators increasingly maintain detailed digital logs of tail number utilization, crew pairings, and maintenance histories precisely because such data has real value—for regulatory compliance, resale documentation, and even sentimental or historical purposes, as this Reddit post demonstrates. The inability to easily answer a seemingly simple question about a flight from 2001 reflects both how far aviation data systems have come and how much operational history from the pre-ADS-B era remains effectively lost to casual public inquiry, preserved only in the private records of airlines, regional carriers, and the FAA's registration archives.