WELL · 42-261-31530 · DISTRICT 4
Santa FE Julian Pasture #4
Kenedy County · Ball Ranch (Vicksburg Cons.) field · Producing · Vertical
Santa FE Julian Pasture #4 (API 42-261-31530) is a well in Kenedy County operated by Abaco Operating LLC, completed April 1, 2010 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit, issued January 20, 2010, permitted to 14,000 ft.
Completion filings report one formation top, including Frio.
No lease production has been reported under this well’s leases.
Operator of record
San Antonio, TX · P-5 Y, filed Sep 4, 2025 · 91 permits on file · (210) 219-8565
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Abaco Operating LLC |
| Production reports | Abaco Operating, LLCthrough Apr 2026 |
| Latest permit | Abaco Operating, LLCJan 20, 2010 |
- 14,000
- total depth, ft
- 1
- permits on file
- Jan 20, 2010
- last permit issued
- Apr 1, 2010
- completed
- 0
- cumulative oil, bbl
- 1.11M
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Apr 2010 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Apr 1, 2010
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: Active
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 |
|---|---|---|---|---|---|---|
| Santa FE Julian Pasture G-4-256036 | Ball Ranch (Vicksburg Cons.) | Abaco Operating, LLC | 1 | 0 | 1.11M | Apr 2010 – Jul 2026 |
Gas, mcf lease total
Last 12 months 30,114 · prior 12 58,219(-48%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Abaco Operating, LLCApr 2010 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 689851-99 | Drill | Abaco Operating, LLC | Jan 15, 2010 | Jan 20, 2010 | Jan 26, 2010 | 14,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-4-256036 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 35 ft elevation.Download CSV →
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 11,927 | 11,938 | Perforated |
| 11,945 | 11,952 | Perforated |
| 11,981 | 11,992 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 10.75 | 3,020 | 14.75 | 1,355 S |
| 7.625 | 9,955 | 9.875 | 287 S |
| 4.5 | 12,265 | 5.875 | 200 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 | Jul 20, 2010 | Apr 28, 2010 | Yes |
| 00 | Jun 3, 2010 | — | — |
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-261-31530 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-261-31530 → 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/26131530, documented in the API reference.