WELL · 42-197-31419 · DISTRICT 9

Quinby #1

Plugged

Hardeman County · Quinby (Chappel) field  · Vertical

Quinby #1 (API 42-197-31419) is a plugged well in Hardeman County, plugged March 9, 2009, last operated by Trio Consulting & Management LLC.

The RRC has issued one drilling permit, issued October 1, 1997, permitted to 8,600 ft.

It was permitted by Trio Operating Company, Inc. and has since transferred to Trio Consulting & Management LLC on the wellbore schedule.

Completion filings report 3 formation tops, including Canyon, Palo Pinto, Mississippian.

Its lease has reported 79.9K barrels of oil since January 1998, last reporting in July 2009.

Operator of record

Trio Consulting & Management LLC

Permitted by Trio Operating Company, Inc.; the EWA schedule now lists a different operator.

Based in
Wichita Falls, TX
P-5 status
Active (A)
P-5 last filed
Oct 23, 2025
Permits on file
351
Phone
(940) 767-2847

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleTrio Consulting & Management LLC
Production reportsTrio Consulting & Management,llcthrough Nov 2008
Latest permitTrio Operating Company, Inc.Oct 1, 1997

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

8,600
total depth, ft
1
permits on file
Oct 1, 1997
last permit issued
Jan 2, 1998
completed
79.9K
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1998 THROUGH Jul 2009

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jan 2, 1998
Shut in
—
Plugged
Mar 9, 2009

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
Quinby O-13-29461Quinby (Chappel)Trio Consulting & Management,llc179.9K0Jan 1998 – Jul 2009

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. 1Trio Operating Company, Inc.Jan 1998 → Dec 2001
  2. 2Trio Consulting & Management,llcJan 2002 → Nov 2008

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
468155-99DrillTrio Operating Company, Inc.Sep 29, 1997Oct 1, 1997Oct 7, 19978,600

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-29461————

Formation tops

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

FormationMD ftSubsea
Canyon3,950-2,492
Palo Pinto5,350-3,892
MississippianMISS. LIME7,750-6,292

Perforations

Perforated and open-hole intervals.

FromToType
8,1188,136Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62553012.25275 S
5.58,1187.875200 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
00Mar 27, 1998Jan 6, 1998Yes
00Mar 18, 1998——

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