WELL · 42-183-31926 · DISTRICT 6

Mackey #1

Y

Gregg County · Oak Hill (Cotton Valley) field · Temp Abandoned  · Vertical

Mackey #1 (API 42-183-31926) is a well in Gregg County operated by Sydri Operating LLC, completed May 22, 2007 and listed as temp abandoned on the RRC schedule.

The RRC has issued one drilling permit, issued March 21, 2007, permitted to 11,250 ft.

It was permitted by Chinn Exploration Company and has since transferred to Sydri Operating LLC on the wellbore schedule.

Completion filings report 7 formation tops, including BMA, Rodessa, Pettit, Travis Peak.

No lease production has been reported under this well’s leases.

Operator of record

Sydri Operating LLC

Permitted by Chinn Exploration Company; the EWA schedule now lists a different operator.

Dallas, TX · P-5 Y, filed Dec 4, 2025 · 46 permits on file · (972) 754-8626

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleSydri Operating LLC
Production reportsTrivium Operating, LLCthrough Feb 2018
Latest permitChinn Exploration CompanyMar 21, 2007

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

11,250
total depth, ft
1
permits on file
Mar 21, 2007
last permit issued
May 22, 2007
completed
0
cumulative oil, bbl
174K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · May 2007 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
May 22, 2007
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 →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Mackey G-6-229395Oak Hill (Cotton Valley)Sydri Operating, LLC10174KMay 2007 – 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.

  1. 1Chinn Exploration CompanyMay 2007 → Jun 2012
  2. 2Trivium Operating, LLCMay 2016 → Feb 2018

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
566013-99DrillChinn Exploration CompanyFeb 26, 2007Mar 21, 2007Mar 23, 200711,250

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-6-229395————

Formation tops

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

FormationMD ftSubsea
BMA6,569-6,198
Rodessa6,622-6,251
Pettit7,122-6,751
Travis Peak7,570-7,199
B Lime9,455-9,084
C Valley9,470-9,099
Taylor10,670-10,299

Perforations

Perforated and open-hole intervals.

FromToType
9,50610,953Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,02411297 S
4.511,0207.8751,500 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 17, 2007Jul 26, 2007Yes
00Sep 12, 2007——

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