WELL · 42-083-31345 · DISTRICT 7

Vaughn, Gary M. #1

Plugged

Coleman County  · Vertical

Vaughn, Gary M. #1 (API 42-083-31345) is a plugged well in Coleman County, plugged April 9, 1978, last operated by Cedar Oil Company.

The RRC has issued 3 drilling permits between 1977 and 1983, permitted to 4,500 ft.

Completion filings report 8 formation tops, including Coleman Junction, Top Home Creek Limestone, Palo Pinto, Top Gardner Sand.

Its lease has reported 3.5K barrels of oil and 27.5K mcf of gas since January 1993, last reporting in July 2026. The lease carries 5 wells, so these are lease totals, not this well alone.

Operator of record

Cedar Oil Company

Based in
Abilene, TX
P-5 status
Active (A)
P-5 last filed
Mar 18, 2026
Permits on file
76
Phone
(325) 692-3731

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsTargo Oil & Gas, Inc.through Jan 2003
Latest permitCedar Oil CompanyAug 16, 1983
4,500
total depth, ft
3
permits on file
Aug 16, 1983
last permit issued
—
completed
3.5K
cumulative oil, bbl
27.5K
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
Apr 9, 1978

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; they carry 5 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Vaughn, Gary M. O-8-20491Coleman County RegularTargo Oil & Gas, Inc.53.5K27.5KJan 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.

  1. 1Cedar Oil CompanyJan 1993 → Jun 1993
  2. 2Targo Oil & Gas, Inc.Jul 1993 → Jan 2003

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
205681-99RecompletionCedar Oil CompanyAug 10, 1983Aug 16, 1983—4,500
175579-99OtherCedar Oil CompanyOct 27, 1982Oct 27, 1982—4,500
14819-99DrillGraham, Keith D.Dec 28, 1977Dec 28, 1977—3,900

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-8-20491————

Formation tops

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

FormationMD ftSubsea
Coleman JunctionBASE COLEMAN JUNCTION1,190752
Top Home Creek Limestone2,600-658
Palo PintoTOP PALO PINTO LIMESTONE3,082-1,140
Top Gardner Sand3,360-1,418
Top Caps Limestone3,376-1,434
Top Gray Sand3,805-1,863
CaddoTOP CADDO LIMESTONE4,000-2,058
EllenburgerTOP ELLENBURGER4,370-2,428

Perforations

Perforated and open-hole intervals.

FromToType
3,6803,685Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62512011.590 S
2.3754,308——
4.54,3707.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
00Feb 13, 1984Dec 6, 1983—
00Jan 12, 1984Jan 14, 1983—

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