WELL · 42-355-06687 · DISTRICT 4
Luby J. P. #59 AF
Nueces County · Luby ( 8080) field · Vertical
Luby J. P. #59 AF (API 42-355-06687) is a permitted well in Nueces County filed by Apache Corporation; no completion report is on file yet.
The RRC has issued 3 drilling permits (amended once) between 1983 and 2001, permitted to 8,418 ft.
It was permitted by Apache Corporation and has since transferred to Alegre Operating Inc. on the wellbore schedule.
Completion filings report 4 formation tops, including Oakville, Catahoula, Anahuac, Frio.
Its 6 leases have reported 3.67K barrels of oil and 124K mcf of gas since January 1993, last reporting in July 2026. The leases carry 12 wells, so these are lease totals, not this well alone.
Operator of record
Permitted by Apache Corporation; the EWA schedule now lists a different operator.
Corpus Chrsti, TX · P-5 Y, filed Apr 4, 2026 · (361) 877-8000
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Alegre Operating Inc. |
| Production reports | Apache Corporationthrough Jun 2002 |
| Latest permit | Apache CorporationOct 10, 2001 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 8,418
- total depth, ft
- 4
- permits on file
- Oct 10, 2001
- last permit issued
- —
- completed
- 3.67K
- cumulative oil, bbl
- 124K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- —
- Shut in
- —
- Plugged
- —
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 6 leases this well is completed on; they carry 12 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Luby, J. P. G-4-45979 | Luby ( 6250) | Alegre Operating, Inc. | 1 | 0 | 0 | Jan 1993 – Jul 2026 |
| Luby, J. P. G-4-190710 | Luby ( 7550) | Alegre Operating, Inc. | 1 | 0 | 103K | Apr 2001 – Jul 2026 |
| Luby, J. P. O-4-7034 | Luby ( F Sand, Lower) | Alegre Operating, Inc. | 2 | 0 | 0 | Jan 1993 – Jul 2026 |
| Luby, J. P. O-4-7328 | Luby ( 8080) | Alegre Operating, Inc. | 2 | 0 | 0 | Jan 1993 – Jul 2026 |
| Luby, J. P. O-4-7429 | Luby ( 6800) | Alegre Operating, Inc. | 5 | 3.67K | 20.7K | Jan 1993 – Jul 2026 |
| Luby, J.P. O-4-10428 | Luby (7170) | Alegre Operating, Inc. | 1 | 0 | 0 | Jan 1993 – Jul 2026 |
No volumes reported on these leases in the last three years.
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Texaco E & P Inc.Jan 1993 → Jun 1993
- 2Apache CorporationJan 1996 → Jun 2002
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 509277-98 | Recompletion | Apache Corporation | Dec 20, 2001 | Oct 10, 2001 | Mar 15, 2001 | 8,400 |
| 509277-99 | Recompletion | Apache Corporation | May 22, 2001 | Oct 10, 2001 | — | 8,406 |
| 232508-99 | Recompletion | Texaco Inc. | Mar 14, 1984 | Mar 15, 1984 | — | 8,418 |
| 225084-99 | Recompletion | Texaco Inc. | Dec 28, 1983 | Dec 29, 1983 | — | 8,418 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-4-45979 | — | — | — | — |
| — | — G-4-190710 | — | — | — | — |
| — | — O-4-7034 | — | — | — | — |
| — | — O-4-7328 | — | — | — | — |
| — | — O-4-7429 | — | — | — | — |
| — | — O-4-10428 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 18 ft elevation.Download CSV →
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 6,662 | 6,667 | Perforated |
| 6,768 | 6,782 | Perforated |
| 7,170 | 7,178 | Perforated |
| 7,522 | 7,526 | Perforated |
| 7,950 | 7,960 | Perforated |
| — | 5,252 | Perforated |
| — | 8,078 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 13.375 | 1,220 | 17.5 | 500 S |
| 13.375 | 1,221 | 17.5 | 500 S |
| 2.875 | 8,400 | 12.25 | 1,300 S |
| 2.875 | 8,400 | — | — |
| 2.875 | 8,406 | 12.5 | — |
| 2.875 | 8,406 | — | — |
| 4.5 | 8,413 | 12.25 | 1,300 sx |
| 2.875 | 8,414 | 12.5 | — |
| 2.875 | 8,414 | — | — |
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 19, 2003 | Jun 5, 2001 | Yes |
| 00 | Oct 4, 2002 | — | — |
| 00 | Feb 21, 2002 | Jun 5, 2001 | Yes |
| 00 | Feb 11, 2002 | — | — |
| 00 | Jun 13, 1984 | Apr 27, 1984 | — |
| 00 | May 4, 1984 | Mar 8, 1984 | Yes |
| 00 | Mar 27, 1984 | Mar 8, 1984 | — |
| 00 | Jan 12, 1984 | Apr 27, 1984 | — |
| 00 | Jan 12, 1984 | Dec 3, 1971 | — |
| 00 | Jan 12, 1984 | Apr 18, 1969 | Yes |
| 00 | Jan 12, 1984 | Mar 17, 1969 | — |
| 00 | Jan 12, 1984 | — | — |
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-355-06687 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-355-06687 → 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/35506687, documented in the API reference.