TEXAS · WELLS · WICHITA COUNTY · API 42-485-46199 · DISTRICT 09

Crackerbox #103

N

Wichita County  · Vertical

Crackerbox #103 (API 42-485-46199) is a permitted well in Wichita County filed by Newport Operating, LLC; no completion report is on file yet.

The RRC has issued one drilling permit, issued May 31, 2019, permitted to 1,999 ft.

Operator of record

Newport Operating, LLC

Based in
Burkburnett, TX
P-5 status
Active (A)
P-5 last filed
Mar 6, 2026
Permits on file
192
Phone
(972) 439-6094

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitNewport Operating, LLCMay 31, 2019
1,999
total depth, ft
1
permits on file
May 31, 2019
last permit issued
—
completed
—
cumulative oil, bbl
—
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
—

Surface location

34.049189, -98.507122 NAD27, as filed

34.049284, -98.507455 WGS84

Google Maps ↗

Permit surface location from the RRC GIS record, referenced to NAD27 as the RRC files it; the WGS84 pair is the same point through NOAA's NADCON grid, and the map link uses it, in Wichita County.

Wells nearby

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

Loading the wells nearby…

Open the full map →

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

Only the permit record exists for this well so far, here and in the RRC's wellbore query. Completion reports, formation tops, lease production, and the scanned filings appear once the operator files a completion report, typically months after drilling. Petrora refreshes the wellbore file weekly, so a filing from the last few days may reach the RRC before it shows here. How long each source takes →

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
853429-99DrillNewport Operating, LLCMay 23, 2019May 31, 2019—1,999

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 →

Nearby wells and their tops

NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM

Draw a cross-section

This well has no tops filed, so it cannot anchor a section; its neighbors can.

Section of the neighbors →

Crackerbox42-485-46191

0.1 KM · Newport Operating, LLC · Section with this well →

Cisco822181
Thomas Sand1,052-49
Gunsight1,283-280
Gunsight1,372-369
Strawn—
Tannehill—
Canyon—
Bluff Creek Sand—

10 TOPS · FIRST 8

Dunn, J. Z.42-485-46099

0.2 KM · Rog Enterprises, LLC · Section with this well →

Cisco940
Tannehill—
Strawn—
KMA—
Gunsight—
Gunsight—
Canyon—
Bluff Creek Sand—

10 TOPS · FIRST 8

Crackerbox42-485-46190

0.2 KM · Newport Operating, LLC · Section with this well →

Cisco868139
Thomas Sand1,218-211
Gunsight1,314-307
Tannehill—
Strawn—
KMA—
Gunsight—
Bluff Creek Sand—

10 TOPS · FIRST 8

Dunn, J. Z.42-485-46027

0.3 KM · Rog Enterprises, LLC · Section with this well →

Gunsight1,310
Thomas Sand—
Gunsight—
KMA—
Strawn—
Tannehill—
Canyon—
Bluff Creek Sand—

10 TOPS · FIRST 8

Dunn, J. Z.42-485-46032

0.3 KM · Rog Enterprises, LLC · Section with this well →

Gunsight1,310
Gunsight1,400
Bluff Creek Sand—
Canyon—
Cisco—
KMA—
Strawn—
Tannehill—

10 TOPS · FIRST 8

Dunn, J. Z.42-485-46029

0.5 KM · Rog Enterprises, LLC · Section with this well →

Tannehill660
Cisco—
Gunsight—
Gunsight—
KMA—
Strawn—
Thomas Sand—
Vogstberger—

10 TOPS · FIRST 8

Dunn, J. Z.42-485-46093

0.8 KM · Rog Enterprises, LLC · Section with this well →

Cisco930
Vogstberger—
Thomas Sand—
Tannehill—
Strawn—
KMA—
Gunsight—
Gunsight—

10 TOPS · FIRST 8

Roller Estate42-485-46041

2.2 KM · Newport Operating, LLC · Section with this well →

Cisco200
Tannehill300
Thomas Sand1,150
Gunsight1,306
Gunsight1,436
Vogstberger—
Canyon—
KMA—

10 TOPS · FIRST 8

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