TEXAS · WELLS · BRAZOS COUNTY · STINGRAY LEASE · API 42-041-32278 · DISTRICT 05
Stingray #2H
Brazos County · Aguila Vado (Eagleford) field · Producing · Horizontal
Stingray #2H (API 42-041-32278) is a horizontal well in Brazos County operated by Wildfire Energy Operating LLC, completed October 7, 2014 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit (amended once), issued May 15, 2014, permitted to 8,962 ft.
It was permitted by Halcon Operating CO., Inc. and has since transferred to Wildfire Energy Operating LLC on the wellbore schedule.
Completion filings report 8 formation tops, including Sparta, Wilcox, Navarro, Austin Chalk.
Its lease has reported 179K barrels of oil and 177K mcf of gas since October 2014, last reporting in July 2026.
Operator of record
Permitted by Halcon Operating Co., Inc.; the EWA schedule now lists a different operator.
- Based in
- Houston, TX
- P-5 status
- Active (A)
- P-5 last filed
- Nov 24, 2025
- Permits on file
- 171
- Phone
- (832) 558-0100
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Wildfire Energy Operating LLC |
| Production reports | Wildfire Energy Operating LLCthrough Mar 2026 |
| Latest permit | Halcon Operating Co., Inc.May 15, 2014 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 8,962
- total depth, ft
- 2
- permits on file
- May 15, 2014
- last permit issued
- Oct 7, 2014
- completed
- 179K
- cumulative oil, bbl
- 177K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Oct 2014 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Oct 7, 2014
- 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.
Lease production
PDQ LEASE REPORTS · REPORTED THROUGH APR 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 |
|---|---|---|---|---|---|---|
| Stingray O-5-4172 | Aguila Vado (Eagleford) | Wildfire Energy Operating LLC | 1 | 179K | 177K | Oct 2014 – Jul 2026 |
Oil, barrels lease total
Last 12 months 3,537 · prior 12 4,162(-15%)
Gas, mcf lease total
Last 12 months 3,192 · prior 12 4,403(-28%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Halcon Operating Co., Inc.Oct 2014 → Feb 2017
- 2Hawkwood Energy Operating, LLCMar 2017 → Mar 2022
- 3Wildfire Energy Operating LLCApr 2022 → Mar 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 784320-98 | Drill | Halcon Operating Co., Inc. | Feb 25, 2015 | May 15, 2014 | Aug 6, 2014 | 9,000 |
| 784320-99 | Drill | Halcon Operating Co., Inc. | Apr 9, 2014 | May 15, 2014 | Aug 6, 2014 | 9,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Oct 7, 2014 | Stingray O-5-4172 | Aguila Vado (Eagleford) | Wildfire Energy Operating LLC | Producing | 8,962 |
Formation tops
As filed on W-2/G-1. Subsea from 291 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| SpartaSPARTA - DISPOSAL | 2,840 | -2,549 |
| WilcoxWILCOX - DISPOSAL | 3,610 | -3,319 |
| NavarroNAVARRO - DISPOSAL | 5,975 | -5,684 |
| Austin ChalkAUSTIN CHALK - LOST CIRCULATION | 7,823 | -7,532 |
| WoodbineWOODBINE - PRODUCTION | 8,168 | -7,877 |
| BudaBUDA - PRODUCTION | — | — |
| EdwardsEDWARDS - DISPOSAL | — | — |
| GeorgetownGEORGETOWN - PRODUCTION | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 9,248 | 9,450 | Perforated |
| 9,498 | 9,700 | Perforated |
| 9,748 | 9,950 | Perforated |
| 9,998 | 10,200 | Perforated |
| 10,248 | 10,450 | Perforated |
| 10,498 | 10,700 | Perforated |
| 10,748 | 10,950 | Perforated |
| 10,998 | 11,200 | Perforated |
| 11,248 | 11,450 | Perforated |
| 11,498 | 11,700 | Perforated |
| 11,750 | 11,950 | Perforated |
| 11,998 | 12,200 | Perforated |
| 12,248 | 12,450 | Perforated |
| 12,498 | 12,700 | Perforated |
| 12,748 | 12,950 | Perforated |
| 12,998 | 13,050 | Perforated |
| 13,160 | 13,237 | Perforated |
| 13,285 | 13,387 | Perforated |
| 13,418 | 13,620 | Perforated |
| 13,668 | 13,870 | Perforated |
| 13,918 | 14,120 | Perforated |
| 14,168 | 14,220 | Perforated |
| 14,330 | 14,419 | Perforated |
| 14,467 | 14,669 | Perforated |
| 14,717 | 14,919 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 9.625 | 4,671 | 12.25 | 1,420 S |
| 5.5 | 15,515 | 8.75 | 1,920 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. About these reports →
| Suffix | Filed | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Aug 13, 2015 | Mar 20, 2015 | Yes |
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-041-32278 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-041-32278 → scanned completion filings
Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward). then paste it into their 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/04132278, documented in the API reference.