WELL · 42-023-30060 · DISTRICT 9

Quisenberry #1A

Plugged

Baylor County · Baylor County Regular field  · Vertical

Quisenberry #1A (API 42-023-30060) is a plugged well in Baylor County, plugged December 20, 2024, last operated by Dry Fork Production CO. LLC.

The RRC has issued one drilling permit, issued August 6, 2014, permitted to 3,999 ft.

Completion filings report 2 formation tops, including Palo Pinto, Strawn.

Its lease has reported 20.2K barrels of oil since November 2012, last reporting in May 2025. The lease carries 3 wells, so these are lease totals, not this well alone.

Operator of record

Dry Fork Production Co. LLC

Wichita Falls, TX · P-5 Y, filed Feb 4, 2026 · 207 permits on file · (940) 704-7200

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleDry Fork Production Co. LLC
Production reportsDry Fork Production Co., LLCthrough Dec 2024
Latest permitDry Fork Production Co., LLCAug 6, 2014
3,999
total depth, ft
1
permits on file
Aug 6, 2014
last permit issued
Sep 30, 2015
completed
20.2K
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Nov 2012 THROUGH May 2025

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Sep 30, 2015
Shut in
—
Plugged
Dec 20, 2024

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 3 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Quisenberry O-13-32614Baylor County RegularDry Fork Production Co., LLC320.2K0Nov 2012 – May 2025

Oil, barrels lease total

Last 12 months 0 · prior 12 283(-100%)

050100150202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Dry Fork Production Co., LLCJan 2013 → Dec 2024

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
790936-99ReenterDry Fork Production Co., LLCJul 3, 2014Aug 6, 2014Sep 25, 20153,999

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-32614————

Formation tops

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

FormationMD ftSubsea
Palo PintoPALO PINTO REEF3,140-1,855
StrawnSTRAWN LIME3,805-2,520

Perforations

Perforated and open-hole intervals.

FromToType
3,1403,180Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62516811115 S
5.54,0307.87550 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
00Dec 15, 2015Dec 4, 2015—

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.

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

0
bbl, last 12 reported months
460K
bbl, all reported
Feb 2025
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000113177H-1 InjectionPlugged Mar 17, 20251,0001,5003,130–3,400

MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS

Last 12 months 0 · prior 12 14,600(-100%)

05001K1.5K20242025

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