WELL LOGS · UNITED STATES · ONE ROW PER LOG

Well logs within 2 mi of API 42-497-00531

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 API 42-497-00531Clear

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.

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

Well DistancemiLogas describedIntervalft, as filedDatereceived
Nelon G. E. (AW) #2HHZ42-497-37999Wise, TX · BKV Barnett LLC0.19Measure While Drilling (MWD)TIFF6,300 to 14,350Jun 6, 2022
Stevens Arthur #1HHZ42-497-36817Wise, TX · Eagleridge Operating LLC0.85SURVEYS CASED HOLETIFF6,050 to 9,095Jun 13, 2012run May 17, 2009
Petty T. F. GU #2HZ42-497-35324Wise, TX · BKV Barnett LLC1.19ResistivityTIFFHIGH RESOLUTION INDUCTION423 to 5,965Feb 23, 2007run Aug 12, 2003
Harrison C. J. a #3HZ42-497-36424Wise, TX · BKV Barnett LLC1.35RESISTIVITYTIFF577 to 6,010May 12, 2011run Apr 4, 2008
Osburn Wendell Gas Unit a #1HZ42-497-35231Wise, TX · BKV Barnett LLC1.60ResistivityTIFFHIGH RESOLUTION ARRAY INDUCTION1,034 to 5,771Aug 17, 2006run Apr 15, 2003
Stearns R. D. #242-497-36211Wise, TX · Texxol Operating Company Inc.1.62RESISTIVITYTIFF343 to 6,983Mar 2, 2010run Feb 20, 2007
Austin R. E. Gas Unit #2HZ42-497-36245Wise, TX · BKV Barnett LLC1.65RESISTIVITYTIFF567 to 6,292Oct 4, 2010run Aug 23, 2007
Harrison C. J. #342-497-34833Wise, TX · BKV Barnett LLC1.66RESISTIVITYTIFF548 to 7,246Aug 19, 2008run Jan 1, 2002
Goodger W. L. #142-497-36215Wise, TX · Texxol Operating Company Inc.1.70RESISTIVITYTIFF638 to 7,016Apr 12, 2010run Mar 21, 2007
Austin R. E. Gas Unit #4HZ42-497-36714Wise, TX · BKV Barnett LLC1.93RESISTIVITYTIFF527 to 6,063Feb 15, 2012run Jan 8, 2009
Ratliff East #242-497-36159Wise, TX · Texxol Operating Company Inc.1.93NEUTRON POROSITYTIFF5,250 to 6,932Feb 22, 2010run Feb 8, 2007
Austin R. E. Gas Unit #6HZ42-497-36669Wise, TX · BKV Barnett LLC1.94SURVEYS CASED HOLETIFF6,157 to 9,990Jan 4, 2012run Dec 10, 2008
Austin R. E. Gas Unit #3HZ42-497-36706Wise, TX · BKV Barnett LLC1.96SURVEYS CASED HOLETIFF6,010 to 6,872Mar 8, 2012run Feb 3, 2009
Austin R. E. Gas Unit #7HZ42-497-36670Wise, TX · BKV Barnett LLC1.97SURVEYS CASED HOLETIFF6,160 to 9,301Jan 4, 2012run Dec 29, 2008
Clark Lizzie #142-497-36214Wise, TX · Texxol Operating Company Inc.1.98RESISTIVITYTIFF641 to 6,982Apr 13, 2010run Mar 7, 2007
Boyd Townsite #242-497-36685Wise, TX · Texxol Operating Company Inc.1.98NEUTRON/DENSITY POROSITYTIFF3,900 to 7,018Oct 1, 2009run Jan 6, 2009
Boyd Townsite #242-497-36685Wise, TX · Texxol Operating Company Inc.1.98RESISTIVITYTIFF622 to 7,028Sep 30, 2009run Jan 6, 2009

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.