XS68
Airport
Sky Lane Ranch
Brenham, Texas

FAA NFDC Information Effective 56-day cycle 07/24/2014 - 9/18/2014

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:XS68
Lat/Lng: 30.2568788889, -96.3285747222
30-15-24.7640N, 096-19-42.8690W
Estimated
Elevation: 290 feet Estimated
Magnetic Variation: 06E, (1990), [3E (2014)]
Sectional: HOUSTON
From City: 7nm NE of Brenham

Operations

Use: Private
Ownership: Privately owned
Activation: 03/1994
Control Tower: no
ARTCC: Houston Center (ZHU)
FSS: Montgomery County FSS (CXO)
Wind Indicator: Unlighted
Landing Fee: no

Communications

Services

Based Aircraft

Single Engine GA: 1
Total: 1

Annual Operations

Total: 0

Ownership

Owner: Charles Wade Lane
Rt 2 Box 432
Brenham, Tx 77833
409-830-0818
Manager: Charles Wade Lane
Rt 2 Box 432
Brenham, Tx 77833
409-830-0818

Runways

Runways: 14/32

Runway 14/32

Length: 1800 feet
Width: 40 feet
Surface: Grass / Sod
End 14 End 32
Displaced Threshold Distance: 400'  
Objects: Powerline Powerline
Object Marking: Marked  
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Height: 25' AGL 30' AGL
Object Distance: 150' Along centerline 800' Along centerline

Procedures

NOTAMs

Additional Remarks


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.