| Stafford Regional Airport | |
| Icao: | KRMN |
| Faa: | RMN |
| Type: | Public |
| Owner-Oper: | Stafford Regional Airport Authority |
| Location: | Stafford, Virginia |
| Coordinates: | 38.3981°N -77.4556°W |
| Elevation-F: | 211 |
| Elevation-M: | 64 |
| Pushpin Map: | USA Virginia#USA |
| Pushpin Relief: | yes |
| Pushpin Map Caption: | Location of airport in Virginia / United States |
| Pushpin Label: | RMN |
| Pushpin Label Position: | right |
| R1-Number: | 15/33 |
| R1-Length-F: | 6,000 |
| R1-Length-M: | 1,829 |
| R1-Surface: | Asphalt |
| Stat-Year: | 2018 |
| Stat1-Header: | Aircraft operations |
| Stat1-Data: | 30,141 |
| Footnotes: | Source: Federal Aviation Administration[1] Virginia department of Aviation[2] |
Stafford Regional Airport is a public airport located three miles (5 km) southwest of the central business district of Stafford, the county seat of Stafford County, Virginia, United States. The airport is southwest of the intersection of Route 630 and U.S. Route 1 near Interstate 95, approximately 40miles south of Washington, D.C., and 60miles north of Richmond. It is owned and operated by the Stafford Regional Airport Authority, an independent body of representatives from Stafford and Prince William Counties and the City of Fredericksburg.[3]
Although most U.S. airports use the same three-letter location identifier for the FAA and IATA, Stafford Regional Airport is assigned RMN by the FAA but has no designation from the IATA (which assigned RMN to Rumginae, Papua New Guinea).[4] [5]
Stafford Regional Airport covers an area of 566acres which contains one asphalt paved runway (15/33) measuring 6,000 x 100 ft (1,829 x 30 m). For the 12-month period ending December 31, 2018, the airport had 30,141 aircraft operations, an average of 83 per day: 93% general aviation and 7% military.
The airport was the site of a fatal accident on February 22, 2006, involving a Lancair Columbia 400 piloted by a private pilot.[6] The pilot and three passengers were killed when the aircraft flew into trees surrounding the runway after an aborted landing attempt via ILS.[7] Following an investigation, the NTSB cited pilot error as the most likely cause of the accident.[8]