WELL LOGS · UNITED STATES · ONE ROW PER LOG

Well logs within 2 mi of Lynn Unit #2H (42-439-34849)

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 Lynn Unit #2H (42-439-34849)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.

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

Well DistancemiLogas describedIntervalft, as filedDatereceived
Lynn Unit #2HHZ42-439-34849Tarrant, TX · BKV North Texas LLC0.55SURVEYS CASED HOLETIFF5,800 to 12,042Dec 7, 2010run Jul 31, 2010
Lynn Unit #2HHZ42-439-34849Tarrant, TX · BKV North Texas LLC0.55SURVEYS CASED HOLETIFF6,000 to 11,020Dec 6, 2010run Jul 12, 2010
TCC #4HHZ42-439-33221Tarrant, TX · TEP Barnett USA LLC0.82ACOUSTIC POROSITYTIFF2,093 to 8,815Nov 14, 2011run Oct 10, 2008
TCC #4HHZ42-439-33221Tarrant, TX · TEP Barnett USA LLC0.82NEUTRON/DENSITY POROSITYTIFF2,093 to 8,815Nov 14, 2011run Oct 10, 2008
TCC #4HHZ42-439-33221Tarrant, TX · TEP Barnett USA LLC0.82RESISTIVITYTIFF2,093 to 8,815Nov 14, 2011run Oct 10, 2008
Lynn Unit #1HHZ42-439-33340Tarrant, TX · BKV North Texas LLC0.83SURVEYS CASED HOLETIFF6,000 to 12,668Feb 18, 2009run Sep 10, 2008
Sue Barnett Unit #4HHZ42-439-34670Tarrant, TX · BKV North Texas LLC0.85RESISTIVITYTIFF5,000 to 11,350Feb 4, 2014run Jan 13, 2013
Sue Barnett Unit #1HHZ42-439-34602Tarrant, TX · BKV North Texas LLC0.93SURVEYS CASED HOLETIFF5,775 to 9,808Jan 11, 2011run Aug 16, 2010
Fulson Colby #2HHZ42-439-37262Tarrant, TX · TEP Barnett USA LLC0.99Gamma RayLAS + TIFF80 to 15,457Sep 23, 2026
Crossroads West #2HHZ42-439-33049Tarrant, TX · TEP Barnett USA LLC1.00NEUTRON/DENSITY POROSITYTIFF2,146 to 6,917May 31, 2011run May 5, 2008
Crossroads West #2HHZ42-439-33049Tarrant, TX · TEP Barnett USA LLC1.00RESISTIVITYTIFF2,146 to 6,917May 31, 2011run May 5, 2008
Sue Barnett Unit #3HHZ42-439-37010Tarrant, TX · BKV North Texas LLC1.51RESISTIVITYTIFF2,091 to 11,576Dec 15, 2015run Apr 3, 2015
Sunbelt B #3HHZ42-439-32781Tarrant, TX · TEP Barnett USA LLC1.53NEUTRON/DENSITY POROSITYTIFF2,101 to 8,530Mar 14, 2011run Jan 14, 2008
Sunbelt B #3HHZ42-439-32781Tarrant, TX · TEP Barnett USA LLC1.53RESISTIVITYTIFF2,101 to 8,561Mar 14, 2011run Jan 14, 2008
Sunbelt B #3HHZ42-439-32781Tarrant, TX · TEP Barnett USA LLC1.53RESISTIVITYTIFF8,050 to 8,584Mar 14, 2011run Jan 14, 2008
Sue Barnett Unit #5HHZ42-439-37011Tarrant, TX · BKV North Texas LLC1.95RESISTIVITYTIFF2,062 to 12,732May 10, 2016run May 25, 2015
Sue Barnett Unit #8HHZ42-439-37025Tarrant, TX · BKV North Texas LLC1.96RESISTIVITYTIFF0 to 13,343Dec 15, 2015run May 9, 2015

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.