TEXAS · WELLS · WICHITA COUNTY · RESEARCH TEST WELL LEASE · API 42-485-42161 · DISTRICT 7C

Research Test Well #1

Plugged

Wichita County · Wichita County Regular field  · Vertical

Research Test Well #1 (API 42-485-42161) is a plugged well in Wichita County, plugged April 6, 2016, last operated by NU-Bore Systems.

The RRC has issued one drilling permit, issued July 18, 1990, permitted to 1,500 ft.

Operator of record

NU-Bore Systems

Based in
Wichita Falls, TX
P-5 status
Inactive (I)
P-5 last filed
Jun 10, 1991
Permits on file
1
Phone
(817) 322-7185

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleNU-Bore Systems
Production reportsnone
Latest permitNU-Bore SystemsJul 18, 1990
1,500
total depth, ft
1
permits on file
Jul 18, 1990
last permit issued
—
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · ON RECORD FROM JAN 1993, THE RECORD'S FIRST MONTH, THROUGH —

On this pageLease production

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
Apr 6, 2016

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.

Wells nearby

Every well with a location on file around this well, in any state, nearest first.

Loading the map…

Open the full map →

Texas locations come from drilling permits, so most older Texas wells have none and are not listed.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH AUG 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
Research Test Well O-13-27936Wichita County RegularNU-Bore Systems100by Jan 1993 – —

No volumes reported on these leases in the last three years.

Wells named Research Test Well

NU-Bore Systems's other wells filed under this lease name in Wichita County, newest permit first. The RRC gives a gas well its own lease number, so the name is what joins the wells of a unit.

Loading the lease's wells

Chain of custody

Operator on the lease's P-4

Each operator named on the P-4 filings for this well's lease (a gas well is its own lease), from the date its filing took effect. The P-4 is filed by lease, so a date before the well was drilled is the lease's.

OperatorFromTo
NU-Bore SystemsSep 20, 1990today

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
375641-99DrillNU-Bore SystemsJul 18, 1990Jul 18, 1990Jul 23, 19901,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—Research Test Well O-13-27936Wichita County RegularNU-Bore SystemsPlugged—

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,51111378 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00Apr 9, 1991Sep 20, 1990—
00Mar 11, 1991——

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 filed since 2004 open from the RRC's log search for this well; none are loaded here for it.

Find logs withinmiles of this well:List →Map →

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