WELL · 42-391-32903 · DISTRICT 2
Fagan #18
Refugio County · Vertical
Fagan #18 (API 42-391-32903) is a permitted well in Refugio County filed by Great Bay Operations, LLC; no completion report is on file yet.
The RRC has issued 3 drilling permits between 2009 and 2012, permitted to 5,650 ft.
Completion filings report 2 formation tops, including Mcfaddin 2700, Mcfaddin (5400' Upper).
Operator of record
Portsmouth, NH · P-5 Y, filed Sep 2, 2016 · 44 permits on file · (603) 767-4766
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | Great Bay Operations, LLCthrough Dec 2010 |
| Latest permit | Great Bay Operations, LLCAug 2, 2012 |
- 5,650
- total depth, ft
- 3
- permits on file
- Aug 2, 2012
- last permit issued
- —
- completed
- 0
- cumulative oil, bbl
- 50.5K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jun 2009 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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Fagan G-2-252334 | McFaddin (5400 Upper) | Allegiant Resources, LLC | 1 | 0 | 43.4K | Jun 2009 – Jul 2026 |
| Fagan G-2-258978 | McFaddin (2750) | Allegiant Resources, LLC | 1 | 0 | 7.11K | Aug 2010 – 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.
- 1Great Bay Operations, LLCOct 2009 → Dec 2010
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 743173-99 | Recompletion | Great Bay Operations, LLC | Jun 20, 2012 | Aug 2, 2012 | — | 5,650 |
| 705504-99 | Recompletion | Great Bay Operations, LLC | Nov 16, 2010 | Nov 24, 2010 | Aug 13, 2010 | 5,650 |
| 681230-99 | Drill | Great Bay Operations, LLC | May 12, 2009 | May 14, 2009 | Jun 5, 2009 | 5,650 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-2-252334 | — | — | — | — |
| — | — G-2-258978 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 60 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| McFaddin 2700 | 2,720 | -2,660 |
| McFaddin (5400' Upper) | 5,145 | -5,085 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 2,720 | 2,726 | Perforated |
| 5,145 | 5,150 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 1,377 | 12.25 | 685 S |
| 5.5 | 5,100 | 7.875 | 260 S |
| 5.5 | 5,636 | 7.875 | 260 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 | Sep 1, 2011 | Sep 2, 2010 | Yes |
| 00 | Feb 23, 2011 | — | — |
| 00 | Jan 4, 2010 | Aug 31, 2009 | Yes |
| 00 | Nov 4, 2009 | — | — |
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-391-32903 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-391-32903 → 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/39132903, documented in the API reference.