Logan
Cache Valley fog, a 4,457-foot airport, training traffic, and cross-state freight routes put visibility and ground access into the first planning pass.
Geography changes the lift plan
Heavy Lift By Location
A helicopter lift is planned around the place where it happens. Airspace, terrain, forecast conditions, staging access, and nearby development can change the usable aircraft, flight path, schedule, and ground plan.
City and state field guides
Read the ground before the aircraft moves
These guides examine what changes from one market to the next. A dense downtown may make crane setup the controlling problem. A mountain site can shift the analysis to density altitude and road access. Coastal work brings different weather windows.
Utah through Washington
20 city guides on this page
Ogden
A high-elevation municipal airport, Hill Air Force Base traffic, lake-edge fog, and mountain terrain make route visibility as important as ground access.
Provo
A 4,497-foot airport, heavy training traffic, mountain recreation, and campus streets put performance and route coordination at the front of the plan.
Salt Lake City
Class B airspace, a 4,231-foot airport, mountain weather, and managed public streets put the flight route and ground footprint under separate reviews.
St. George
A high-desert airport, triple-digit summer heat, flash-flood exposure, and fast-changing access conditions make the usable window a site-specific calculation.
Barre
Granite facilities, reused industrial buildings, flood-sensitive access, and a cold-temperature airport make the ground route as important as the flight route.
Bennington
Mountains in every quadrant, airport approach controls, industrial parcels, and a cross-state corridor make height and route review inseparable.
Burlington
Class C airspace, lake-influenced wind, institutional campuses, and controlled city streets put aviation and ground permissions on parallel tracks.
Rutland
A regional airport south of town, city-owned utilities, redevelopment sites, and rain-sensitive mountain roads make access verification a first-pass task.
St. Albans
A compact industrial center, one main north-south arterial, regional airport limits, and strong valley wind make route coordination the first constraint.
Arlington
Dense mixed-use districts, Class B airspace, narrow public-way windows, and a flood-prone Potomac setting put the flight route and street plan on the same schedule.
Bristol
A freight-connected border city gives way quickly to ridges, valleys, developed slopes, and municipal streets where the last mile can decide the plan.
Richmond
Class C airspace, river and rail corridors, interstate freight, and city-controlled streets make the support route as important as the load path.
Roanoke
Roanoke sits west of the Blue Ridge, where a towered two-runway airport, through freight routes, and city-controlled rights-of-way put the flight plan and support footprint in one review.
Virginia Beach
Coastal wind and water, military-airfield compatibility zones, resort-season street limits, and dispersed growth areas make access timing a first-pass constraint.
Kennewick
Columbia River industry, high-volume freight roads, summer visibility hazards, and load-specific street permits make delivery and weather checks first-pass work.
Olympia
A public general-aviation airport, wet-season access risks, state-route permitting, and construction runoff controls all need answers before aircraft-day planning.
Seattle
Class B airspace, active port terminals, dense public streets, and exposed utility infrastructure put the flight route and ground plan on the same review track.
Spokane
Winter access, a busy freight corridor, river crossings, and airport-side obstacle notices put delivery routing beside the flight review.
Vancouver
Pearson Field sits beneath Portland traffic, while the Columbia River port and city streets carry separate access rules that must be settled before a work window.
Planning paths
Follow the work, not a sales pitch
From the technical library
