WELL LOGS · UNITED STATES · ONE ROW PER LOG

Well logs within 2 mi of Pritchard -B- #13 (42-233-33281)

Well logs loaded into Petrora from the regulators' log indexes, newest received first: what each measures, whether it is a digital LAS file or an image, the interval filed for it, and the formations it spans by the well's own tops. Loaded so far for Texas; more states and data sources will follow. Petrora lists these logs; each well's page links to the regulator for the files.

Within0.5 mi1 mi2 mi3 mi5 mi10 mi25 miof Pritchard -B- #13 (42-233-33281)Clear

Distances are to the nearest location on file for each well (a horizontal has several along its path), in miles. Locations are surface and path points as mapped, not bottom-hole surveys.

19 LOG FILES ON 12 WELLS · A LOG'S LAS AND IMAGE IN ONE ROW · PAGE 1 OF 1

Well DistancemiLogas describedIntervalft, as filedDatereceived
Pritchard -B- #13HZ42-233-33281Hutchinson, TX · Burk Royalty Co. Ltd.hereNEUTRON/DENSITY POROSITYTIFF752 to 2,623Jun 11, 2009run Jan 2, 2008
Pritchard -B- #13HZ42-233-33281Hutchinson, TX · Burk Royalty Co. Ltd.hereRESISTIVITYTIFF752 to 2,636Jun 11, 2009run Jan 2, 2008
Pritchard -B- #13HZ42-233-33281Hutchinson, TX · Burk Royalty Co. Ltd.hereRESISTIVITYTIFF752 to 2,646Jun 11, 2009run Jan 2, 2008
Pritchard -B- #13HZ42-233-33281Hutchinson, TX · Burk Royalty Co. Ltd.hereRESISTIVITYTIFF2,654 to 3,004Jun 11, 2009run Jan 5, 2008
Pritchard B #1142-233-33225Hutchinson, TX · Burk Royalty Co. Ltd.0.18RESISTIVITYTIFF788 to 3,776Feb 18, 2011run Dec 20, 2007
McDowell #1942-233-33468Hutchinson, TX · Burk Royalty Co. Ltd.0.50NEUTRON/DENSITY POROSITYTIFF729 to 3,562Sep 1, 2015run Aug 17, 2012
Pritchard B #1242-233-33227Hutchinson, TX · Burk Royalty Co. Ltd.0.57NeutronTIFF784 to 3,673Feb 13, 2018
Stewart #29AHZ42-233-33423Hutchinson, TX · Burk Royalty Co. Ltd.0.95RESISTIVITYTIFF681 to 2,708Dec 10, 2010run Sep 30, 2009
Stewart #29AHZ42-233-33423Hutchinson, TX · Burk Royalty Co. Ltd.0.95RESISTIVITYTIFF2,700 to 3,050Dec 9, 2010run Oct 2, 2009
Harrington #1042-233-33352Hutchinson, TX · Burk Royalty Co. Ltd.1.70RESISTIVITYTIFF772 to 3,689Jun 26, 2009run Jun 12, 2008
Harrington #1042-233-33352Hutchinson, TX · Burk Royalty Co. Ltd.1.70RESISTIVITYTIFF772 to 3,699Jun 26, 2009run Jun 12, 2008
Harrington #1142-233-33484Hutchinson, TX · Burk Royalty Co. Ltd.1.70NeutronTIFF726 to 3,414Feb 13, 2018
Lucas #3142-233-33345Hutchinson, TX · Burk Royalty Co. Ltd.1.86RESISTIVITYTIFF1,438 to 3,711Jun 27, 2011run Apr 28, 2008
Harrington #942-233-33351Hutchinson, TX · Burk Royalty Co. Ltd.1.90RESISTIVITYTIFF747 to 3,695Sep 2, 2009run Jul 4, 2008
Lucas #12AHZ42-233-33420Hutchinson, TX · Burk Royalty Co. Ltd.1.94RESISTIVITYTIFF700 to 2,869Dec 10, 2010run Aug 25, 2009
Lucas #12AHZ42-233-33420Hutchinson, TX · Burk Royalty Co. Ltd.1.94RESISTIVITYTIFF700 to 2,880Dec 10, 2010run Aug 25, 2009
Lucas #12AHZ42-233-33420Hutchinson, TX · Burk Royalty Co. Ltd.1.94RESISTIVITYTIFF2,887 to 3,202Dec 9, 2010run Aug 28, 2009
McDowell C #942-341-33299Moore, TX · Pantera Energy Company1.96RESISTIVITYTIFF2,720 to 3,076May 5, 2015run Oct 10, 2014
Castleman B #1R42-341-32974Moore, TX · Burk Royalty Co. Ltd.1.99ResistivityTIFFHIGH RESOLUTION INDUCTION LOG2,745 to 3,098Feb 13, 2007run Jul 17, 2006

About this data

Well logs loaded into Petrora from the regulators' log indexes, so far for Texas, with more states and data sources to follow; not necessarily every log that exists. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it. A formation is spanned where the log's filed interval overlaps it in the well's own formation tops; both are measured depths as filed, so a horizontal's lateral is counted in the formation it ends in. Kinds are read from the regulator's description of each log, not from its curves. The date is when the log entered the RRC's imaged log database; a run date is shown where the index gives a different one (mostly logs before 2017: since digital filing began that year, the index gives the filing date for both). Nothing is estimated.

Developers: this page as JSON is GET /v1/data/logs, documented in the API reference.