TEXAS · WELLS · UPTON COUNTY · MCELROY RANCH 134 LEASE · API 42-461-37383 · DISTRICT 6E
McElroy Ranch 134 #2SE
Upton County · Spraberry (Trend Area) field · Shut In · Vertical
- Fields on the latest permit · any of 3
- Spraberry (Trend Area) · Wilshire (Consolidated) · Wilshire (Wolfcamp)
- Not one formation; the well must be completed in one of them, and no target formation is stated.
Mcelroy Ranch 134 #2SE (API 42-461-37383) is a well in Upton County operated by Apache Corporation, completed November 27, 2011 and listed as shut in on the RRC schedule, shut in December 1, 2024.
The RRC has issued one drilling permit, issued April 29, 2011, permitted to 10,602 ft.
Completion filings report 3 formation tops, including Wolfcamp, Strawn, Atoka.
Its lease has reported 39.4K barrels of oil and 427K mcf of gas since November 2011, last reporting volume in May 2024.
Operator of record
- Based in
- Houston, TX
- P-5 status
- Active (A)
- P-5 last filed
- Dec 3, 2025
- Permits on file
- 9,758
- Phone
- (713) 954-5500
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Apache Corporation |
| Production reports | Apache Corporationthrough May 2024 |
| Latest permit | Apache CorporationApr 29, 2011 |
- 10,602
- total depth, ft
- 1
- permits on file
- Apr 29, 2011
- last permit issued
- Nov 27, 2011
- completed
- 39.4K
- cumulative oil, bbl
- 427K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · NOV 2011 THROUGH MAY 2024
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Nov 27, 2011
- Shut in
- Dec 1, 2024
- 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.
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 lease this well is completed on; this well is the only one on it.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| McElroy Ranch 134 O-9-17735 | Spraberry (Trend Area) | Apache Corporation | 1 | 39.4K | 427K | Nov 2011 – May 2024 |
Gas, mcf lease total
Last 12 months 0 · prior 12 0
Oil, barrels lease total
Last 12 months 0 · prior 12 0
Wells named McElroy Ranch 134
Apache Corporation's other wells filed under this lease name in Upton 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 wellsChain of custody
Every operator that reported production on this well's lease, in order.
- 1Apache CorporationNov 2011 → May 2024
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 715029-99 | Drill | Apache Corporation | Apr 26, 2011 | Apr 29, 2011 | Sep 12, 2011 | 11,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Nov 27, 2011 | McElroy Ranch 134 O-9-17735 | Spraberry (Trend Area) | Apache Corporation | Shut In · shut in Dec 1, 2024 | 10,602 |
Formation tops
As filed on W-2/G-1. Subsea from 2,835 ft elevation.Download CSV →
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 7,672 | 10,468 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 13.375 | 467 | 17.5 | 450 S |
| 8.625 | 5,461 | 11 | 1,225 S |
| 5.5 | 10,602 | 7.875 | 1,250 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 →
| Suffix | RRC record date | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Feb 25, 2013 | Jan 11, 2012 | Yes |
Well logs
1 log loaded from the RRC's log index, 1 of it with a digital LAS file, the latest received Oct 17, 2017. 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 described | Files | Intervalft, as filed | Datereceived | SizeMB |
|---|---|---|---|---|
| Gamma RaySpans Wolfcamp, Strawn, Atoka | LAS + TIFF | 5,470 to 10,586 | Oct 17, 2017 | 5.78 + 0.81 |
"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.
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.
- Wellbore filings for 42-461-37383 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-461-37383 → scanned completion filings
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/46137383, documented in the API reference.