WELL · 42-341-32923 · DISTRICT 10

Jansyn #4

Plugged

Moore County · Panhandle Moore County Field field  · Vertical

Jansyn #4 (API 42-341-32923) is a plugged well in Moore County, plugged September 13, 2010, last operated by Fortay Inc..

The RRC has issued one drilling permit (amended twice), issued February 25, 2005, permitted to 3,750 ft.

It was permitted by Fortay Inc. and has since transferred to Fortay Inc. on the wellbore schedule.

Completion filings report 2 formation tops, including Brown Dolomite, Moore County Lime.

Its lease has reported 117K barrels of oil and 261K mcf of gas since January 2005, last reporting in July 2026. The lease carries 7 wells, so these are lease totals, not this well alone.

Operator of record

Fortay Inc.

Permitted by Fortay Inc.; the EWA schedule now lists a different operator.

Sunray, TX · P-5 Y, filed Jan 4, 2026 · 59 permits on file · (806) 930-4533

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleFortay Inc.
Production reportsFortay, Inc.through Jun 2018
Latest permitFortay Inc.Feb 25, 2005

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

3,750
total depth, ft
3
permits on file
Feb 25, 2005
last permit issued
Jul 20, 2005
completed
117K
cumulative oil, bbl
261K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 2005 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jul 20, 2005
Shut in
—
Plugged
Sep 13, 2010

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Jansyn O-14-7549Panhandle Moore County FieldFortay, Inc.7117K261KJan 2005 – 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. 1Fortay Inc.Jan 2005 → Apr 2007
  2. 2Fortay, Inc.May 2007 → Jun 2018

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
558228-97DrillFortay Inc.Jun 6, 2005Feb 25, 2005Jun 27, 20053,750
558228-98DrillFortay Inc.May 3, 2005Feb 25, 2005Jun 27, 20053,750
558228-99DrillFortay Inc.Feb 25, 2005Feb 25, 2005Jun 27, 20053,750

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-14-7549————

Formation tops

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

FormationMD ftSubsea
Brown Dolomite2,842713
Moore County Lime3,086469

Perforations

Perforated and open-hole intervals.

FromToType
3,4443,548Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,59312.25825 S
5.53,6517.875190 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
00Apr 20, 2006Dec 21, 2005Yes
00Jan 26, 2006——

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