Taliaferro Field
Ardmore, Oklahoma

FAA NFDC Information Effective 56-day cycle 09/14/2017 - 11/9/2017

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks


FAA Identifier:OK23 (Oscar-Kilo-Two-Three)
Lat/Lng: 34.1983, -97.2311666667
34-11-53.8800N, 097-13-52.2000W
Estimated by OWNER on 11/06/2006
Elevation: 930 feet Estimated by OWNER on 11/06/2006
Magnetic Variation: [4E (2017)]
From City: 5nm NW of Ardmore


Use: Private
Airspace Analysis: CONDITIONAL
Provided Clear 20:1 Approaches, All Traffic Remain West of Runway and South of the Road; and Monitor Frequency 122.75.
Ownership: Privately owned
Activation: 01/2006
Control Tower: no
ARTCC: Fort Worth Center (ZFW)
FSS: Mc Alester FSS (MLC)
Wind Indicator: Lighted
Landing Fee: no



Based Aircraft

Total: 0

Annual Operations

Total: 0


Owner: Jimmy Taliaferro
9627 Brock Rd
Ardmore, Ok 73401
Manager: Eric Faliaferro
7189 Prairie Valley
Ardmore, Ok 73401


Runways: 17/35

Runway 17/35

Length: 1100 feet
by Owner on 11/06/2006
Width: 55 feet
Surface: Grass / Sod
End 17 End 35
Right Hand Pattern: Yes  
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach



Additional Remarks

All Traffic Remain West of Runway and South of Road That Lies Between Colby Field and Taliaferro Field.
All Traaffic Monitor Frequency 122.75.

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.