TEXAS · WELLS · REEVES COUNTY · API 42-389-35186 · DISTRICT 7B

Cheyenne #1

On schedule

Reeves County · Alpine High (Cons) field · Producing  · Vertical

Fields on the latest permit · any of 2
Phantom (Wolfcamp) · Sandbar (Bone Spring)
Not one formation; the well must be completed in one of them, and no target formation is stated. The district's wildcat field is also on the permit.

Cheyenne #1 (API 42-389-35186) is a well in Reeves County operated by Apache Corporation, completed July 3, 2016 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued April 4, 2016, permitted to 10,296 ft.

Completion filings report 10 formation tops, including Bell Canyon, Cherry Canyon, Brushy Canyon, Bone Spring.

Its 2 leases have reported 20.2K barrels of oil and 2.9M mcf of gas since June 2016, last reporting volume in August 2026. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

Apache Corporation

Based in
Houston, TX
P-5 status
Active (A)
P-5 last filed
Dec 3, 2025
Permits on file
9,759
Phone
(713) 954-5500

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleApache Corporation
Production reportsApache Corporationthrough Aug 2026
Latest permitApache CorporationApr 4, 2016
10,296
total depth, ft
1
permits on file
Apr 4, 2016
last permit issued
Jul 3, 2016
completed
20.2K
cumulative oil, bbl
2.9M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · JUL 2016 THROUGH AUG 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jul 3, 2016
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active (A)

Surface location

No coordinates on the permit record yet. The RRC's GIS record usually lands within days of issuance; historical master-file permits never carry one.

Wells nearby

Every well with a location on file around this well, in any state, nearest first.

Loading the map…

Open the full map →

Texas locations come from drilling permits, so most older Texas wells have none and are not listed.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH AUG 2026

Texas reports oil by lease, not by well. These are the 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Cheyenne G-10-285378Alpine High (Cons)Apache Corporation120.2K2.9MJul 2016 – Aug 2026
Cheyenne O-10-48536Alpine High (Cons)Apache Corporation100Jun 2016 – —

Gas, mcf lease total

Last 12 months 69,336 · prior 12 143,560(-52%)

010K20K30K202420252026

Wells named Cheyenne

Apache Corporation's other wells filed under this lease name in Reeves County, newest permit first. The RRC gives a gas well its own lease number, so the name is what joins the wells of a unit.

Loading the lease's wells

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Apache CorporationJul 2016 → Aug 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
814750-99DrillApache CorporationMar 31, 2016Apr 4, 2016Apr 27, 201615,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Jul 3, 2016Cheyenne G-10-285378Alpine High (Cons)Apache CorporationProducing10,296
Jun 13, 2016Cheyenne O-10-48536Alpine High (Cons)Apache CorporationNot on Schedule—

Formation tops

As filed on W-2/G-1. Subsea from 3,112 ft elevation.Download CSV →

FormationMD ftSubsea
Bell Canyon4,422-1,310
Cherry Canyon5,266-2,154
Brushy Canyon6,137-3,025
Bone SpringBONE SPRINGS6,883-3,771
Wolfcamp8,762-5,650
Barnett9,509-6,397
Mississippian9,921-6,809
Woodford10,046-6,934
CastileCASTILLE——
Delaware——
DelawareDELAWARE CONSOLIDATED GAS——
DelawareFORD-DELAWARE——

Perforations

Perforated and open-hole intervals.

FromToType
10,45514,108Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3752,00517.52,260 S
9.6258,71512.251,065 S
5.514,1938.751,480 S

Completion filings

W-2 and G-1 reports on record in the RRC wellbore file, newest first. The suffix identifies the wellbore or completion event. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00Jan 4, 2019Oct 1, 2018Yes
00Aug 24, 2017Feb 25, 2017Yes

Well logs

1 log loaded from the RRC's log index, the latest received Apr 30, 2019. Gamma ray. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.

Open the RRC's log search for this well ↗
Logas describedFiles Intervalft, as filedDatereceivedSizeMB
Gamma RaySpans WoodfordTIFF10,455 to 14,108Apr 30, 20196.88

"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.

Find logs withinmiles of this well:List →Map →

Search the well logs loaded into Petrora →

The source documents

Petrora holds the structured record. The scanned filings live at the RRC; these links open its search already filled in for this API.

The logs loaded for this well are under Well logs, with the RRC's log search for it. The University Lands library has no per-well link: then paste it into its search.

About this data

Permits from the RRC OGA049M master and daily daf420 files; wellbore and operator of record from the EWA schedule, weekly; completions, formation tops, casing, and perforations from the dbf900 wellbore file; production from PDQ lease reports, which lag two to three months; injection from UIC permits, H-10 reports, and TexNet daily volumes; earthquakes from the TexNet catalog.

New to these records? How to read a well page · API numbers · completion reports and tops · why production is by lease

Developers: this page as JSON is GET /v1/data/wells/38935186, documented in the API reference.