AL26
Heliport
Bryant Culberson
Tuscaloosa, Alabama

FAA NFDC Information Effective 56-day cycle 02/22/2024 - 4/18/2024

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:AL26
Lat/Lng:33.2059516667, -87.5277833333
33-12-21.4260N, 087-31-40.0200W
Estimated by Faa-Est Imagery on 05/05/2014
Elevation:283 feet Estimated
Magnetic Variation:01E,(1985), [-3W (2024)]
Sectional:ATLANTA
From City:3nm E of Tuscaloosa

Operations

Use:Private
Medical.
Airspace Analysis:CONDITIONAL
VFR Pvt Use; Coord Use of Heli with Bhm Gado; 2-Way Radio Coms Estabd with Tcl Air Traffic Control Tower Prior to Entering/Departing Control Zone/Airport Traffic Area.
Ownership:Publicly owned
Activation:08/1979
Control Tower:no
ARTCC:Atlanta(ZTL)Atlanta Center
FSS:Anniston FSS(ANB)
Wind Indicator:Lighted
Beacon:Green, White & Yellow. Rotating Beacon Schedule Irregular
Landing Fee:no

Communications

Services

Based Aircraft

Total:0

Annual Operations

Total:0

Ownership

Owner:Dch Regional Medical Center
809 University Blvd East
Tuscaloosa, Al 35401
205-759-7189
Manager:Bill Cassels, Administraton
Druid City Hospital, 809 University Blvd East
Tuscaloosa, Al 35403
205-759-7189

Runways

Runways:H1

Runway H1

Length:50 feet
by Faa-Est Imagery on 05/05/2014
Width:50 feet
Surface:Porland Cement Concrete
Surface Treatment:NONE

Procedures

NOTAMs

Additional Remarks

Long Distance Call to FSS 205-758-3628.
for Cd Contact Atlanta ARTCC at 770-210-7692.

This information is current as of the date at the top of the page. These pages are valid for all US airports, based on information from FAA National Flight Data Center. Weather information is provided based on AvnWx Data Sources. NOTAM information is from FAA's NAIMES data portal.

As with most information on this website, this page is generated based on FAA data, with automatic translations done via computer. You can also directly read the A/FD via the green icon link at the top of the page, which is the FAA text, and sometimes provides a different translation of codes. Please email me (using link at top-right of this page) if you see information which is confusing, misleading, or wrong....Or have suggestions for additions/changes.

Comments from the user community are clearly noted as such this page, are for informational purposes only, may be wrong and/or out-of-date, and must not be used as a sole source for critical decision making. See Privacy Policy and Conditions of Use.