TEXAS · WELLS · LOVING COUNTY · API 42-301-36731 · DISTRICT 08
Avalanche 29-40 Unit #12H
Loving County · Horizontal
Avalanche 29-40 Unit #12H (API 42-301-36731) is a permitted horizontal well in Loving County filed by Anadarko E&P Onshore LLC; no completion report is on file yet.
The RRC has issued one drilling permit, issued January 24, 2024, permitted to 13,000 ft.
Operator of record
- Based in
- Houston, TX
- P-5 status
- Active (A)
- P-5 last filed
- Oct 22, 2025
- Permits on file
- 4,576
- Phone
- (713) 215-7000
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | none |
| Latest permit | Anadarko E&P Onshore LLCJan 24, 2024 |
- 13,000
- total depth, ft
- 1
- permits on file
- Jan 24, 2024
- last permit issued
- —
- completed
- —
- cumulative oil, bbl
- —
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- —
- Shut in
- —
- Plugged
- —
Surface location
31.717581, -103.439706 NAD27, as filed
31.717710, -103.440159 WGS84
Permit surface location from the RRC GIS record, referenced to NAD27 as the RRC files it; the WGS84 pair is the same point through NOAA's NADCON grid, and the map link uses it, in Loving County.
Wells nearby
Every well with a location on file around this one, in any state, nearest first.
Loading the wells nearby…
Texas locations come from drilling permits, so most older Texas wells have none and are not listed.
Only the permit record exists for this well so far, here and in the RRC's wellbore query. Completion reports, formation tops, lease production, and the scanned filings appear once the operator files a completion report, typically months after drilling. Petrora refreshes the wellbore file weekly, so a filing from the last few days may reach the RRC before it shows here. How long each source takes →
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 896636-99 | Drill | Anadarko E&P Onshore LLC | Jan 18, 2024 | Jan 24, 2024 | — | 13,000 |
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-301-36731 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-301-36731 → scanned completion filings
Log images filed since 2004 open from the RRC's log search for this well; none are loaded here for it. The University Lands library has no per-well link: then paste it into its search.
Nearby wells and their tops
NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM
Draw a cross-section
This well has no tops filed, so it cannot anchor a section; its neighbors can.
Section of the neighbors →Yokum UL 19-4 A42-301-34373
0.7 KM · Anadarko E&P Onshore LLC · Section with this well →
| Delaware | 4,895 | -2,131 |
| Bell Canyon | 4,920 | -2,156 |
| Cherry Canyon | 5,884 | -3,120 |
| Brushy Canyon | 7,216 | -4,452 |
| Bone Spring | 10,337 | -7,573 |
| Wolfcamp | 11,338 | -8,574 |
| Strawn | — | |
| Pennsylvanian | — |
10 TOPS · FIRST 8
Yokum UL 19-4 B42-301-34376
0.7 KM · Anadarko E&P Onshore LLC · Section with this well →
| Delaware | 4,895 | -2,131 |
| Bell Canyon | 4,920 | -2,156 |
| Cherry Canyon | 5,884 | -3,120 |
| Brushy Canyon | 7,216 | -4,452 |
| Bone Spring | 10,310 | -7,546 |
| Wolfcamp | 11,320 | -8,556 |
| Atoka | — | |
| Pennsylvanian | — |
10 TOPS · FIRST 8
Shock-N-Awe Unit 29-4142-301-34406
1.1 KM · Anadarko E&P Onshore LLC · Section with this well →
| Delaware | 4,901 | -2,126 |
| Bell Canyon | 4,903 | -2,128 |
| Cherry Canyon | 5,865 | -3,090 |
| Brushy Canyon | 7,193 | -4,418 |
| Bone Spring | — | |
| Wolfcamp | — | |
| Strawn | — | |
| Red Bluff | — |
10 TOPS · FIRST 8
Shock-N-Awe Unit 29-4142-301-34407
1.1 KM · Anadarko E&P Onshore LLC · Section with this well →
| Delaware | 4,901 | -2,126 |
| Bell Canyon | 4,903 | -2,128 |
| Cherry Canyon | 5,865 | -3,090 |
| Brushy Canyon | 7,193 | -4,418 |
| Bone Spring | 8,492 | -5,717 |
| Bone Spring | 9,707 | -6,932 |
| Bone Spring | 10,340 | -7,565 |
| Wolfcamp | — |
10 TOPS · FIRST 8
University 19-8 A42-301-34384
1.3 KM · Anadarko E&P Onshore LLC · Section with this well →
| Bell Canyon | 4,906 | -2,158 |
| Delaware | 4,907 | -2,159 |
| Brushy Canyon | 5,008 | -2,260 |
| Cherry Canyon | 5,887 | -3,139 |
| Bone Spring | 9,415 | -6,667 |
| Wolfcamp | 11,209 | -8,461 |
| Atoka | — | |
| Strawn | — |
10 TOPS · FIRST 8
University 19-8 B42-301-34385
1.3 KM · Anadarko E&P Onshore LLC · Section with this well →
| Delaware | 4,903 | -2,155 |
| Bell Canyon | 4,903 | -2,155 |
| Brushy Canyon | 5,005 | -2,257 |
| Cherry Canyon | 5,861 | -3,113 |
| Bone Spring | 9,441 | -6,693 |
| Wolfcamp | 11,209 | -8,461 |
| Strawn | — | |
| Red Bluff | — |
10 TOPS · FIRST 8
Helga 19-0-4-40 A42-301-36699
1.3 KM · Anadarko E&P Onshore LLC · Section with this well →
| Bell Canyon | 4,963 | -2,224 |
| Delaware | 4,963 | -2,224 |
| Red Bluff | 5,838 | -3,099 |
| Cherry Canyon | 5,896 | -3,157 |
| Brushy Canyon | 7,074 | -4,335 |
| Bone Spring | 8,557 | -5,818 |
| Bone Spring | 9,655 | -6,916 |
| Bone Spring | 10,322 | -7,583 |
10 TOPS · FIRST 8
Helga 19-0-4-40 B42-301-36701
1.3 KM · Anadarko E&P Onshore LLC · Section with this well →
| Bell Canyon | 4,948 | -2,208 |
| Delaware | 4,948 | -2,208 |
| Red Bluff | 5,825 | -3,085 |
| Cherry Canyon | 5,885 | -3,145 |
| Brushy Canyon | 7,082 | -4,342 |
| Bone Spring | 8,557 | -5,817 |
| Wolfcamp | 11,291 | -8,551 |
| Pennsylvanian | — |
10 TOPS · FIRST 8
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/30136731, documented in the API reference.