WELL · 42-409-33147 · DISTRICT 4
Berry Ranch #1
San Patricio County · Meehan (Frio) field · Producing · Vertical
Berry Ranch #1 (API 42-409-33147) is a well in San Patricio County operated by Aurora Resources Corporation, completed January 13, 2026 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit, issued September 5, 2025, permitted to 5,700 ft.
Completion filings report 3 formation tops, including Miocene (undifferentiated), Catahoula, Vicksburg.
Its lease has reported 4.96K barrels of oil since January 2026, last reporting in July 2026.
Operator of record
Corpus Christ, TX · P-5 Y, filed Jan 4, 2026 · 223 permits on file · (361) 947-3730
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Aurora Resources Corporation |
| Production reports | Aurora Resources Corporationthrough Apr 2026 |
| Latest permit | Aurora Resources CorporationSep 5, 2025 |
- 5,700
- total depth, ft
- 1
- permits on file
- Sep 5, 2025
- last permit issued
- Jan 13, 2026
- completed
- 4.96K
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 2026 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Jan 13, 2026
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: X
Surface location
27.933903, -97.726655
OpenStreetMap → · Google Maps →
Permit surface location from the RRC GIS record, in San Patricio County.
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 |
|---|---|---|---|---|---|---|
| Berry Ranch O-4-14271 | Meehan (Frio) | Aurora Resources Corporation | 1 | 4.96K | 0 | Jan 2026 – Jul 2026 |
Oil, barrels lease total
Last 12 months 4,955 · prior 12 0
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Aurora Resources CorporationJan 2026 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 909764-99 | Drill | Aurora Resources Corporation | Aug 8, 2025 | Sep 5, 2025 | Nov 11, 2025 | 5,700 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-4-14271 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 22 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Miocene (undifferentiated)MIOCENE-LAGARTO-OAKVILLE - INJEC | 2,000 | -1,978 |
| CatahoulaCATAHOULA-ANAHUAC - INJECTION/DI | 3,500 | -3,478 |
| CatahoulaCATAHOULA-FRIO - INJECTION/DISPO | 4,000 | -3,978 |
| Vicksburg | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 5,506 | 5,513 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 897 | 12.25 | 635 S |
| 5.5 | 5,815 | 7.875 | 475 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 | Mar 16, 2026 | Jan 27, 2026 | 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-409-33147 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-409-33147 → 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.
Nearby wells and their tops
NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM
Draw a cross-section
This well's tops beside its 5 nearest neighbours, subsea-aligned so they line up regardless of surface terrain.
Barrett-Berry42-409-33115
0.2 KM · Hurd Enterprises, Ltd. · Section with this well →
| Catahoula | 3,980 | -3,950 |
| Vicksburg | — | |
| Catahoula | — | |
| Miocene (undifferentiated) | — |
Blackberry42-409-33105
0.9 KM · Hurd Enterprises, Ltd. · Section with this well →
| Catahoula | 4,100 | -4,078 |
| Catahoula | — | |
| Vicksburg | — | |
| Miocene (undifferentiated) | — |
Mejia Unit42-355-34116
2.2 KM · Forza Operating, LLC · Section with this well →
| Miocene (undifferentiated) | 2,060 | -2,040 |
| Catahoula | 3,650 | -3,630 |
| Catahoula | — | |
| Vicksburg | — |
Fischer Ranch42-409-33139
2.4 KM · Harris Energy Services, LLC · Section with this well →
| Miocene (undifferentiated) | 2,030 | -2,013 |
| Catahoula | 2,730 | -2,713 |
| Catahoula | 3,550 | -3,533 |
| Vicksburg | — |
Klatt42-409-33131
4.6 KM · Cimarron Engineering, LLC · Section with this well →
| Miocene (undifferentiated) | 1,720 | -1,617 |
| Catahoula | 3,678 | -3,575 |
| Catahoula | 3,888 | -3,785 |
| Vicksburg | 6,086 | -5,983 |
Cardwell42-355-34171
7.9 KM · Cimarron Engineering, LLC · Section with this well →
| Miocene (undifferentiated) | 1,466 | -1,375 |
| Catahoula | 2,110 | -2,019 |
| Catahoula | 4,122 | -4,031 |
| Vicksburg | — |
Burrows, J.C. & J.S.42-409-03767
7.9 KM · Wagner Oil Company · Section with this well →
| 5200 Frio Middle | 5,000 | -4,890 |
| Massive Frio | 5,600 | -5,490 |
Cottingham42-355-34179
8.1 KM · Cimarron Engineering, LLC · Section with this well →
| Miocene (undifferentiated) | 1,978 | -1,878 |
| Catahoula | 2,544 | -2,444 |
| Catahoula | 4,250 | -4,150 |
| Vicksburg | 7,298 | -7,198 |
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/40933147, documented in the API reference.