89XS
Heliport
Joe Rye
Pearland, Texas

FAA NFDC Information Effective 56-day cycle 03/21/2024 - 5/16/2024

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:89XS
Lat/Lng:29.5852327778, -95.3035477778
29-35-06.8380N, 095-18-12.7720W
Estimated
Elevation:49 feet Estimated
Magnetic Variation:06E,(1985), [2E (2024)]
Sectional:HOUSTON
From City:2nm NW of Pearland

Operations

Use:Private
Ownership:Privately owned
Activation:01/1979
Attended:All year Mon-Sat 0700-1800 (local)
Control Tower:no
ARTCC:Houston(ZHU)Houston Center
FSS:Montgomery County FSS(CXO)
Wind Indicator:None
Landing Fee:no

Communications

Services

Based Aircraft

Single Engine GA:2
Helicopter GA:1
Total:3

Annual Operations

Total:0

Ownership

Owner:Joe Rye
6626 Scott Lane Rt 3A Box 54B
Pearland, Tx 77581
Manager:Eduardo Acuna
6626 Scott Lane Rt 3A Box 54B
Pearland, Tx 77581
713-485-2644

Runways

Runways:H1

Runway H1

Length:290 feet
Width:113 feet
Surface:Grass / Sod
Surface Treatment:NONE

Procedures

NOTAMs

Additional Remarks

for Cd Contact Houston ARTCC at 281-230-5622.

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.