Joint Base Elmendorf-Richardson: Difference between revisions
Jump to navigation
Jump to search
John Stanton (talk | contribs) No edit summary |
John Stanton (talk | contribs) m Text replace - "width="500"" to "width="-500" height="-500"" |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 23: | Line 23: | ||
{| | {| | ||
| | | | ||
<googlemap version="0.9" lat="61.25139" lon="-149.80639" zoom="11" width="500" type="map" scale="yes" overview="yes" controls="large" icons="http://www.fortwiki.com/mapicons/icon{label}.png"> | <googlemap version="0.9" lat="61.25139" lon="-149.80639" zoom="11" width="-500" height="-500" type="map" scale="yes" overview="yes" controls="large" icons="http://www.fortwiki.com/mapicons/icon{label}.png"> | ||
(A) 61.25139, -149.80639, Elmendorf Air Force Base | (A) 61.25139, -149.80639, Elmendorf Air Force Base | ||
(F) 61.2541, -149.6952, Fort Richardson (2) | (F) 61.2541, -149.6952, Fort Richardson (2) | ||
| Line 38: | Line 38: | ||
{{PageFooter}} | {{PageFooter}} | ||
{{DEFAULTSORT: | {{DEFAULTSORT:Elmendorf–Richardson}} | ||
[[Category:All]] | [[Category:All]] | ||
[[Category:Alaska Joint Bases]] | [[Category:Alaska Joint Bases]] | ||
[[Category:Alaska All]] | [[Category:Alaska All]] | ||
[[Category:Alaska Borough of | [[Category:Alaska Borough of Anchorage]] | ||
[[Category:Active Military Installation]] | [[Category:Active Military Installation]] | ||
[[Category:Joint Bases]] | [[Category:Joint Bases]] | ||
[[Category:{{PAGENAME}}]] | [[Category:{{PAGENAME}}]] | ||
Latest revision as of 18:17, 7 January 2019
|
Joint Base Elmendorf–Richardson (2010-Active) - Joint Base Elmendorf–Richardson (JBER) is a composite administrative management of support functions for the DoD installations in the Anchorage area located at Elmendorf Air Force Base. The component installations retain their separate historic identities but the support functions are jointly managed by the 673d Air Base Wing of the United States Air Force. Joint Base Elmendorf–Richardson achieved full operational capability on 30 Jul 2010.
Links: |