WELL · 42-321-31983 · DISTRICT 3

Allegro-Buckeye #1

Plugged

Matagorda County · Duncan Slough (Frio Cons.) field  · Vertical

Allegro-Buckeye #1 (API 42-321-31983) is a plugged well in Matagorda County, plugged February 27, 2023, last operated by Gaither Petroleum Corporation.

The RRC has issued one drilling permit, issued October 20, 2003, permitted to 11,900 ft.

It was permitted by Allegro Investments, Inc. and has since transferred to Gaither Petroleum Corporation on the wellbore schedule.

Completion filings report 2 formation tops, including Frio, 1st Discorbis (Top).

Operator of record

Gaither Petroleum Corporation

Permitted by Allegro Investments, Inc.; the EWA schedule now lists a different operator.

Katy, TX · P-5 Active, filed Jan 30, 2026 · 117 permits on file · (281) 994-5400

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleGaither Petroleum Corporation
Production reportsExpro Engineering, Inc.through Nov 2014
Latest permitAllegro Investments, Inc.Oct 20, 2003

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

11,900
total depth, ft
1
permits on file
Oct 20, 2003
last permit issued
Apr 8, 2008
completed
0
cumulative oil, bbl
1.1M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 2004 THROUGH Dec 2023

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Apr 8, 2008
Shut in
—
Plugged
Feb 27, 2023

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 →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Allegro-Buckeye G-3-202774Duncan Slough (Frio Cons.)Gaither Petroleum Corporation101.1MFeb 2004 – Dec 2023

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.

  1. 1Allegro Investments, Inc.Feb 2004 → Sep 2007
  2. 2Expro Engineering, Inc.Jan 2008 → Nov 2014

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
537656-99DrillAllegro Investments, Inc.Oct 20, 2003Oct 20, 2003Nov 28, 200311,900

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-3-202774————

Formation tops

As filed on W-2/G-1. Subsea from 40 ft elevation.Download CSV →

FormationMD ftSubsea
FrioMIDDLE FRIO (BASE)6,160-6,120
1ST Discorbis (Top)11,180-11,140

Perforations

Perforated and open-hole intervals.

FromToType
11,49611,516Perforated
11,65111,657Perforated
11,71511,720Perforated
11,75111,758Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
1650——
10.752,02014.751,200 S
7.62510,4509.875245 S
4.511,8446.75380 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 →

SuffixFiledW-2 / G-1 dateLogs referenced
00Sep 11, 2008Jun 16, 2008—
00Sep 27, 2004Jul 22, 2004Yes
00Aug 16, 2004——

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.

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/32131983, documented in the API reference.