Laurence G Hanscom Field
Bedford, United StatesBED / KBED
Regional airport · 53 direct destinations · 2 runways · longest runway 7,011 ft
67 °F · CloudySource: METAR observation via the NOAA Aviation Weather Center
Route
Bedford → Greensboro
BED
BedfordLaurence G Hanscom Field
BedfordLaurence G Hanscom FieldGSOGreensboroPiedmont Triad International Airport
GreensboroPiedmont Triad International Airport- Distance
- 638 mi
- Estimated flight time
- ~1h 45m
Same local time in Bedford and Greensboro.
No nonstop connection observed
Our route data contains no observed nonstop flight from Bedford to Greensboro. That does not rule out a one-stop journey; see the direct destinations of Bedford for the options.
About this route
- Domestic route: both airports are in the same country.
- Direct destinations observed from Bedford: 53.
- Direct destinations observed from Greensboro: 40.
The airports on this route
Piedmont Triad International Airport
Greensboro, United StatesGSO / KGSO
Regional airport · 40 direct destinations · 3 runways · longest runway 10,000 ft
84 °F · Partly cloudySource: METAR observation via the NOAA Aviation Weather Center
Alternative airports for this journey
Same journey, a different airport nearby - with an observed direct connection.
About the route from Bedford to Greensboro
The distance between Laurence G Hanscom Field (BED) and Piedmont Triad International Airport (GSO) is approximately 638 mi; no direct connection has been observed in our route data.
Frequently asked questions about this route
- How far is Bedford from Greensboro by air?
- The great-circle distance between Laurence G Hanscom Field and Piedmont Triad International Airport is approximately 638 mi.
- Is there a direct connection from Bedford to Greensboro?
- No direct connection between BED and GSO has been observed in our route data. That does not rule out a one-stop journey.
- What is the current time difference between Bedford and Greensboro?
- Same local time in Bedford and Greensboro.
Where this data comes from
The route data comes from the flight archive (ADS-B, adsb.lol): which connections actually flew over the last twelve full months and who flew them, combined with our own airport, runway, and airline datasets. It is reference data about observed routes - not a current timetable and no claim about bookability.
The flight archive of the last twelve months has nothing for this route, so we say nothing about frequency.
Route data updated on October 11, 2026.