WELL · 42-009-39236 · DISTRICT 9

Kunkel J. M. -B- #13

Y

Archer County · Archer County Regular field · Producing  · Vertical

Kunkel J. M. -B- #13 (API 42-009-39236) is a well in Archer County operated by Just Oil & Gas Inc., completed December 7, 1985 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued November 13, 1985, permitted to 1,200 ft.

It was permitted by Mmd Oil CO. and has since transferred to Just Oil & Gas Inc. on the wellbore schedule.

Completion filings report one formation top, including Gs Lime.

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

Operator of record

Just Oil & Gas Inc.

Permitted by MMD Oil Co.; the EWA schedule now lists a different operator.

Based in
Graham, TX
P-5 status
Active – Extension (X)
P-5 last filed
Jun 25, 2026
Permits on file
1
Phone
(940) 550-4324

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleJust Oil & Gas Inc.
Production reportsJust Oil & Gas, Inc.through Mar 2026
Latest permitMMD Oil Co.Nov 13, 1985

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

1,200
total depth, ft
1
permits on file
Nov 13, 1985
last permit issued
Dec 7, 1985
completed
2.6K
cumulative oil, bbl
96
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Dec 7, 1985
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active – Extension (X)

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Kunkel, J. M. -B- O-13-192Archer County RegularJust Oil & Gas, Inc.22.6K96Jan 1993 – Jul 2026

Oil, barrels lease total

Last 12 months 698 · prior 12 45(+1451%)

050100202420252026

Chain of custody

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

  1. 1MMD Oil Co.Jan 1993 → Dec 2000
  2. 2E & W ProductionJan 2001 → May 2018
  3. 3Just Oil & Gas, Inc.Apr 2025 → Mar 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
290122-99DrillMMD Oil Co.Nov 12, 1985Nov 13, 1985—1,200

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-192————

Formation tops

As filed on W-2/G-1. Download CSV →

FormationMD ft
GS Lime1,140

Perforations

Perforated and open-hole intervals.

FromToType
1,1481,151Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
4.51,1837.875240 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 6, 1986Jan 14, 1986Yes
00Jan 24, 1986——

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