NV78
Heliport
Remsa/Care Flight
Reno, Nevada

FAA NFDC Information Effective 56-day cycle 11/13/2014 - 1/8/2015

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:NV78
Lat/Lng: 39.5010225, -119.751855
39-30-03.6810N, 119-45-06.6780W
Estimated
Elevation: 4400 feet Estimated
Magnetic Variation: 16E, (1990), [14E (2014)]
Sectional: SAN FRANCISCO
From City: 1nm E of Reno

Operations

Use: Private
Airspace Analysis: CONDITIONAL
Provided Pvt Use; VFR; Routes of Ingress/Egress Restricted to 360 Deg only; Heliport Markings & Lighting in Accordance with FAA Guidance & Coordinate Operations with Reno Cannon ATCT.
Ownership: Privately owned
Activation: 12/1992
Attended: Continuous
Control Tower: no
ARTCC: Oakland Center (ZOA)
FSS: Reno FSS (RNO)
Wind Indicator: Unlighted
Beacon: Sunset-Sunrise (local time)
Clear (Unlighted Land Airport)
Landing Fee: no

Communications

UNICOM: 123.050

Services

Based Aircraft

Helicopter GA: 1
Total: 1

Annual Operations

Total: 0

Ownership

Owner: Reg Emergency Medical Service
450 Edison Way
Reno, Nv 89502
775-858-5700
Manager: Temple Fletcher, Prog Dir
450 Edison Way
Reno, Nv 89502
775-858-5700

Runways

Runways: H1

Runway H1

Length: 75 feet
Width: 75 feet
Surface: Porland Cement Concrete
Runway Lights Edge Intensity: Perimter Lights.

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.